Hi, my pulumi program is stuck creating a new stac...
# general
a
Hi, my pulumi program is stuck creating a new stack? I am running pulumi up on a new stack. Is there something wrong with app.pulumi.com?
g
Are you on Node 12 perhaps? There’s a recent issue causing “hangs” with a recent Node 12 version.
If so, can you try downgrading to Node 10 (the current LTS version) and see if you get the same issue?
a
Yea, I can try that. I am on Node 12, but I thought the issue was Catalina only lol
yup, on node v12.11.1
Ok, switching to node v10 with nvm works. brew has node 12 as "stable" which was the issue
g
Thanks for confirming. Yea, we initially thought it was limited to Catalina but doesn’t seem to be.
c
Hmm - we are seeing our GKE up script hang as well.
Not on Catalina though
Is it possibly related?
Node is v12.11.1
Yep - switching back to node 10 seems to fix the issue for us
g
Which OS are you on?
l
@crooked-jelly-50877. I'm working on a fix for this now. Question: do you ever call
new aws.Provider(...)
anywhere in your project?
c
Mac OS 10.14.6
No - this is deploying on GKE
hanging on some rpc call
I think it might be
Copy code
return gcp.container.getEngineVersions({
        location: gcp.config.zone,
        versionPrefix: config.k8sVersion,
    });
l
No - this is deploying on GKE
That's fine. My fix will be most likely to work if you are not doing
new aws.Provider()
anywhere.
c
we also have EKS deployments.. let me check
l
you can potentially try to unblock yourself now by passing in
{ async: true }
to
getEngineVersions
. however, you will have to deal with result coming back as a Promise.
c
No aws.Provider() that I can see
l
my fix should make it so that your above code now works without a hang.
c
Node 10 is fine for now 😉
That unblocks us