-
Notifications
You must be signed in to change notification settings - Fork 132
Don't update machine status to terminating on deletion failure #995
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
Conversation
|
@takoverflow Thank you for your contribution. |
aaronfern
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
The release note looks a bit vague, can you please relook at it?
Consider something like (does not need to be this, please add what you feel is appropriate)
Fixed a bug in the MachineSet controller where the machine status was set to `Terminating` even if attempt to delete the machine object failed.
aaronfern
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
/lgtm
elankath
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks - this was a gap in the current code that caused stuck in Terminating phase esp when VM's could not be launched for some cases.
What this PR does / why we need it:
Upon failure in deletion of a machine, it should not transition to
Terminatingphase.Which issue(s) this PR fixes:
Fixes #984
Special notes for your reviewer:
Release note: