-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[release-1.7] 🐛 Machine Controller should try to retrieve node on delete #11043
[release-1.7] 🐛 Machine Controller should try to retrieve node on delete #11043
Conversation
/lgtm |
LGTM label has been added. Git tree hash: 993763a348abe2c177f1be39a5e4a273b7f728b5
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Consider this scenario: * Machine is created * InfraMachine is created * MachineHealthCheck is set to 10 minutes * [10 minutes pass] * Machine is marked as needing remediation * Machine and InfraMachine goes into deletion flow * Node finally joins the cluster, say 10 minutes + few seconds * InfraMachine is still waiting for VM to be deleted * Machine keeps retrying to delete, but `nodeRef` was never set * Machine, InfraMachine go away (finalizer removed) * Node object sticks around in the cluster This changset allows the Machine controller to look into the cluster during deletion flow if the Node eventually got created before the infrastructure provider was able to fully delete the machine. Signed-off-by: Vince Prignano <[email protected]>
7260565
to
38df8bc
Compare
Had to push a very minor unit test fix on this PR: daf0e4a (@chrischdi please double check when you're around) |
/lgtm |
LGTM label has been added. Git tree hash: 6cc312e5190b564090f36cdfc5888e5c29d0a5ef
|
👍 lgtm |
This is an automated cherry-pick of #11032
/assign sbueringer