-
Notifications
You must be signed in to change notification settings - Fork 61
Stacks operations got interrupted on pod termination #795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have been digging further into this problem, it looks like the pulumi operator itself replaces/updates the workspace/statefulset during active operations :-( During the destroy operation it get interrupted by updating the statefulset during the destroy operation, marks it even as fail, and then removes the finalizer from the stack. :-( Operator log
workspace log
|
Thanks for looking into and reporting this issue and providing detailed logs. We'll look further into resolving this issue. |
I wonder if this has the same root cause as #786. The stack controller generally does nothing when there's an active update, so a more low-level perturbation of the workspace seems to be happening. Thanks again for the tremendous reports, stay tuned. |
@project0 I have a PR ready, feel free to comment. |
What happened?
Stack operations got interrupted on pod termination, this can lead to orphan resources as stack operation are not finished. This is especially crucial on ephemeral resources that should be cleaned up on stack deletion, currently it just leaves the resources orphan -.-
Example
not relevant, that happens with any program with Stack CRD in my case.
Output of
pulumi about
n/a
Additional context
I am using argocd applicationset to ramp up a namespace and the program/stack. I guess the pod is terminated by argo in this case. However, there should never be a situation that operations leave undesired stack states (especially on delete).
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: