https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
Does this happen across all stacks or just one? Have you tried turning on verbose logging?
Copy code
pulumi up --logtostderr -v=9 --debug
What version of pulumi plugins are you running? 
pulumi plugin ls -p
Also, can you share the 
requirements.txt
and/or 
package.json
?
f
Hi Tushar. Just this stack, I tried verbose logging but could not see anything interesting. It just stops. Currently going through and upgrading plugins to see if that helps.
Copy code
pulumi-aws 3.38.1 has requirement pulumi<3.0.0,>=2.15.0, but you'll have pulumi 3.2.1 which is incompatible.
Version numbers are a little confusing.
Same behavior.
Copy code
NAME    KIND      VERSION  SIZE    INSTALLED       LAST USED
aws     resource  4.3.0    258 MB  6 minutes ago   4 minutes ago
docker  resource  3.0.0    40 MB   11 minutes ago  11 minutes ago
python  language           21 MB   5 days ago      1 second ago

TOTAL plugin cache size: 319 MB
I blasted my 
venv
and reinstalled everything. Here is my 
requirements.txt
Copy code
grpcio>=1.33.2,!=1.30.0
pulumi>=3.0.0,<4.0.0
pulumi-aws>=3.0.0
pulumi-docker>=3.0.0
looks like it is picking up an older aws plugin from cache on some things.
c
Since you are running on pulumi cli 
3.2.1
can you update the 
requirements.txt
for 
pulumi-aws
From: 
pulumi-aws>=3.0.0
TO: 
pulumi-aws>=4.0.0,<5.0.0
f
Sure, no effect though, it already had an appropriate version installed. For some existing resources it looks to be pulling an old plugin. Something with the state is confusing the planner. I can create a new stack no problem. Sadly this is my foundation stack that all the others depend on.
Hi @gentle-diamond-70147, thanks for reaching out on Twitter. I've exhausted my Pulumi diagnostic abilities and am not sure what to do next.
g
Hey! I probably should have looked here first... 🙂
Let me catch up on this thread.
f
Sure thing. It isn't a complex stack. I'm wondering if the lambda layer, which is the reason i was updating, is causing the issue.
g
Does this happen during 
pre
, 
up,
refresh
... all of the above?
f
preview. refresh ran ok, have not tried up because of past scars. trying now.
up
and 
preview
both get stuck
g
Can you share the full 
pre
output? and with the logging that Tushar mentioned earlier?
DM is fine if you'd like
4 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by