getting `an unhandled error occurred: Program exit...
# general
s
getting
an unhandled error occurred: Program exited with non-zero exit code: 1
from a stack that hasn’t changed in months. identical stack is working in our other account. made sure to update pulumi as well as the nodejs provider and all other dependencies, seeing absolutely nothing in verbose output to indicate what the problem is. indeed, seeing “Planner decided not to update after diff”, so no idea what could have broken here. how should i proceed?
g
Is it possible that an old run against the stack might not have completed? Or a resource fell over between the last time the stack was run and now?
s
there are no pending locks on the statefile. the manifest shows it as being updated by
v3.22.1
today, which was a refresh i did earlier which completed successfully. i guess i can try rolling back to a previous checkpoint, but that shouldn’t be necessary. i’m happy to dig in more, but there’s absolutely nothing in the logs to indicate what’s going wrong. i’m just running
pulumi preview --debug --logtostderr -v 10
here’s the output if it helps https://gist.github.com/tychedelia/829ed6967cdd9ee05c4c330da3be0563 we’re using the s3 backend
g
Hm, interesting. I'm going to take that gist back to the engineering team to figure out what's up as I'm not finding anything in there that would explain it either 😕
s
thanks, laura. i appreciate it
g
Our engineers asked if you'd open an issue so they can help figure out what's happening and why we aren't producing a better error (why we're not capturing the error to help debug from that layer in the process). Mind raising a flag in https://github.com/pulumi/pulumi/issues/new?assignees=&labels=kind%2Fbug&template=0-bug-report.md and tagging me (https://github.com/nimbinatus) to ensure it gets escalated?
s
sure thing, will do in a minute
👍 1
g
Got it; thanks! I'm passing it on right now
❤️ 1
s
thanks again
g
You're very welcome! Please let me know if it stalls, and I'll go poking around 😄