We're using the

automation_api

on

node.js

to create resources on AWS and K8s. We have two classes that performs the text-book Pulumi flow. Each one independently is working fine. The weird issue pops when we're running them one after the other. Doesn't matter which one is the first, the second one is always failing with a

grpc

related error:

Exception has occurred: Error: 14 UNAVAILABLE: No connection established
  at Object.callErrorFromStatus (.../node_modules/@grpc/grpc-js/src/call.ts:81:24)

Some more metadata: • There are two different stacks for each one. • There is no paralleling, one is done and only then the other starts • We're using an inline function • Pulumi version: 3.3.0 Any ideas what could go wrong? Thanks!

If I had to guess this is likely some kind of automation API bug related to static global state being set in the first run that isn't being cleaned up, and is then causing the second run to fail. You might want to open an issue and see if you can get a small repro together

I’ve been struggling with similar looking grpc errors. In our case, the fix was downgrading to 3.2.1 for both the CLI and SDK https://github.com/pulumi/pulumi/issues/6998

@proud-pizza-80589 - no luck on downgrading but thanks. @bored-oyster-3147 - Yes, agree that it looks like state related issue. opened an issue. thanks.