Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mitigate Azure VM Deletion Race Condition #255

Closed
vlerenc opened this issue Apr 17, 2019 · 3 comments
Closed

Mitigate Azure VM Deletion Race Condition #255

vlerenc opened this issue Apr 17, 2019 · 3 comments
Labels
kind/bug Bug priority/2 Priority (lower number equals higher priority)

Comments

@vlerenc
Copy link
Member

vlerenc commented Apr 17, 2019

As was identified, kube-controller-manager implementation for Azure interferes with MCM VM deletion and due to an infrastructure race condition may leave VMs in inconsistent state, breaking all automation. The infrastructure team is committed to fix the race condition, but we planned in the meanwhile to implement a mitigation (evict, then delete the pods, then detach all disks, then delete the VM).
@vlerenc vlerenc added priority/critical Needs to be resolved soon, because it impacts users negatively kind/bug Bug labels Apr 17, 2019
@prashanth26
Copy link
Contributor

Hi @vlerenc ,

From an MCM perspective, this issue has been resolved by this PR - #248. You can take a look at the release notes to confirm expected behavior.

@vlerenc
Copy link
Member Author

vlerenc commented Apr 23, 2019

Thank you very much @prashanth26. :-)

@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 25, 2019
@prashanth26
Copy link
Contributor

Closing this issue WRT #248

@gardener-robot gardener-robot added priority/2 Priority (lower number equals higher priority) and removed priority/critical Needs to be resolved soon, because it impacts users negatively labels Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Bug priority/2 Priority (lower number equals higher priority)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vlerenc @prashanth26 @gardener-robot-ci-1 @gardener-robot