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.

Pulumi Community

image.png

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?

Does this happen across all stacks or just one?
Have you tried turning on <https://www.pulumi.com/docs/troubleshooting/#verbose-logging|verbose logging>?
```pulumi up --logtostderr -v=9 --debug```
What version of <https://www.pulumi.com/docs/reference/cli/pulumi_plugin_ls/|pulumi plugins> are you running? `pulumi plugin ls -p`
Also, can you share the `requirements.txt` and/or `package.json`?

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.

```pulumi-aws 3.38.1 has requirement pulumi&lt;3.0.0,&gt;=2.15.0, but you'll have pulumi 3.2.1 which is incompatible.```
 Version numbers are a little confusing.

Same behavior.
```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`

```grpcio&gt;=1.33.2,!=1.30.0
pulumi&gt;=3.0.0,&lt;4.0.0
pulumi-aws&gt;=3.0.0
pulumi-docker&gt;=3.0.0```


looks like it is picking up an older aws plugin from cache on some things.

Since you are running on pulumi cli `3.2.1` can you update the `requirements.txt` for `pulumi-aws`
From: `pulumi-aws&gt;=3.0.0`
TO:  `pulumi-aws&gt;=4.0.0,&lt;5.0.0`

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 <@UDEJ1F5SQ>, thanks for reaching out on Twitter. I've exhausted my Pulumi diagnostic abilities and am not sure what to do next.

Hey! I probably should have looked here first... :slightly_smiling_face:

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.

Does this happen during `pre`, `up,` `refresh`... all of the above?

preview. refresh ran ok, have not tried up because of past scars.

trying now.

Can you share the full `pre` output? and with the logging that Tushar mentioned earlier?