This message was deleted.
# generals
sparse-intern-71089
04/21/2020, 10:58 PMThis message was deleted.
r
red-match-15116
04/21/2020, 11:02 PMI think the Recovering from an Interrupted Update + Manually Editing Your Deployment sections might be helpful here: https://www.pulumi.com/docs/troubleshooting/#interrupted-update-recovery
o
orange-policeman-59119
04/21/2020, 11:07 PMI think that ends up being a huge amount of work, when what I really want is behavior like:
"Oh, this resource is already deployed with the right namespace and name? Okay, I'll import it automatically!"
orange-policeman-59119
04/21/2020, 11:07 PMI can't stress this enough:
when the helm chart hangs in our CI system, the state is completely absent
orange-policeman-59119
04/21/2020, 11:08 PMI cannot edit my deployment because the CI system kills the process and no checkpointed state is persisted anywhere
orange-policeman-59119
04/21/2020, 11:08 PM(we have a 1 hour timeout on our CI jobs)
r
red-match-15116
04/21/2020, 11:14 PMI hear ya. I think folks have hit this same issue but perhaps want a different outcome behavior?
https://pulumi-community.slack.com/archives/C84L4E3N1/p1587207659355600
https://github.com/pulumi/pulumi/issues/4265
Feel free to upvote if that's in line with what you'd like to see, or open up an issue if it's not.
w
white-balloon-205
04/22/2020, 1:38 AM
@orange-policeman-59119 just to check - are you using the Pulumi service backend of a cloud storage (blob) backend?
it hangs and doesn’t serialized the checkpoint
This should never happen. I’d love to understand exactly what is causing this for you.
o
orange-policeman-59119
04/22/2020, 9:09 PMCloud storage (blob) backend
orange-policeman-59119
04/22/2020, 9:09 PMI switched to basically doing
rsync $bucket $localdir
pulumi login --local $localdir
# do operation
pulumi logout
rsync $localdir $bucket
orange-policeman-59119
04/22/2020, 9:10 PMI was deploying the
prometheus-operatororange-policeman-59119
04/22/2020, 9:11 PMI also think there was some Google Cloud Storage rate limiting happening which caused a hang - when I tried running directly against the GCS bucket backend I observed a lot of 429 rateLimitExceeded errors in my console
w
white-balloon-205
04/24/2020, 6:09 AM
Yeah - there have been many reports on this recently. Appears something changed in the GCS side recently. Discussing how to address that for Pulumi at https://github.com/pulumi/pulumi/issues/4258.
I would guess that is the root of the problems here