I'm having an issue with `v3.Release` resources ha...
# kubernetes
l
I'm having an issue with
v3.Release
resources hanging indefinitely on a
pulumi up
. A lot of the rest of my stack depends on this resource as it deploys CRDs, and it seems to affect all stacks containing it. When ran with debug, the preview just idles at
Copy code
I1203 14:08:40.497660    6047 eventsink.go:78] eventSink::Infoerr(<{%reset%}>I1203 14:08:40.471633    6417 rpc.go:77] Marshaling property for RPC[Provider[kubernetes:helmrelease].Update(urn:pulumi:bm4::benchmarks-eks::ebx:component:Cluster/cluster$kubernetes:helm.sh/v3:Release::prometheus-crds).inputsAndComputed]: waitForJobs={false}
Anyone seen this before?
If I change variables in that resource, I am able to update that specific resource if I skip the preview, but then it'll hang on marshaling properties for it so the deployment never finishes
I'm getting to the point where I'm probably going to have to do some hardcore state surgery to extract this resource out of all the stacks, because it will not stop hanging
Unfortunately that didn't work either. Looks like it's the first kube resource in the stack that hangs indefinitely rather than that specific resource...
h
are you able to install the same chart (with the same values) via helm CLI?
l
Yes. It's installed fine - the issue is updating the stack it's in. This program has been working fine for months, but as of last week some time, Pulumi hangs indefinitely trying to update the stack (not the chart - the chart is identical). I've made a little bit of progress in trying to narrow down what's causing it, but it's really difficult because apparently some of my provider versions changed, so I can't target anything, and there's no --target-ignore so I can update everything else while this resource is freaking out. It's actually kind of maddening to debug, because there isn't really a way to just... Ask Pulumi what the hell it's doing right now. The debug logs aren't very helpful because no logs are being produced, because it's hanging. But what is it hanging on?!
h
what version of the k8s provider are you using currently, and what version did you have when it was working?
l
Apologies, it looks like the debug hanging on k8s resources was a red herring. I actually had a function hanging elsewhere 😞
This ended up being due to a promise (inside a pulumi input) that never resolved. For future reference, is there a way to identify which inputs Pulumi is waiting for?
h
awesome, glad to hear you got to the bottom of it. you might be interested in the recent debugger support we added https://www.pulumi.com/docs/iac/concepts/debugging/