https://pulumi.com logo
#general
Title
# general
f

fast-whale-9064

05/12/2021, 2:58 PM
Also having trouble with a hang during a preview. Was on a late 2.x version, now on 3.2.1. Running a trace indicates it's stuck in planning. It didn't complete, it was cancelled. I may try just letting it run, but clearly something is wrong. Any suggestions on diagnosing?
c

cool-fireman-90027

05/12/2021, 3:40 PM
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

fast-whale-9064

05/12/2021, 3:44 PM
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

cool-fireman-90027

05/12/2021, 6:44 PM
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

fast-whale-9064

05/12/2021, 6:50 PM
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

gentle-diamond-70147

05/12/2021, 6:59 PM
Hey! I probably should have looked here first... 🙂
Let me catch up on this thread.
f

fast-whale-9064

05/12/2021, 7:05 PM
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

gentle-diamond-70147

05/12/2021, 7:24 PM
Does this happen during
pre
,
up,
refresh
... all of the above?
f

fast-whale-9064

05/12/2021, 7:30 PM
preview. refresh ran ok, have not tried up because of past scars. trying now.
up
and
preview
both get stuck
g

gentle-diamond-70147

05/12/2021, 7:46 PM
Can you share the full
pre
output? and with the logging that Tushar mentioned earlier?
DM is fine if you'd like
2 Views