-
Notifications
You must be signed in to change notification settings - Fork 81
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
Make infra-flow deletion more resilient #925
Conversation
We've recently seen a few edge cases where some referenced resources were already successfully deleted but the deletion flow was not finished completely. Upon retry the deletion was now stuck since the supposedly still existing resources could not be found anymore. With this commit, those resources will be assumed to have been successfully deleted and the deletion flow will continue.
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.
nit
err = client.FilterNotFoundError(err) | ||
|
||
if err != nil { | ||
return err | ||
} |
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.
if client.FilterNotFoundError(err) {
return err
}
|
||
// If we do not find any loadbalancers, assume the resource group was successfully deleted and we | ||
// are done. | ||
err = client.FilterNotFoundError(err) |
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.
same as other 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.
/lgtm
How to categorize this PR?
/area robustness
/kind enhancement
/platform azure
What this PR does / why we need it:
We've recently seen a few edge cases where some referenced resources were already successfully deleted but the deletion flow was not finished completely. Upon retry the deletion was now stuck since the supposedly still existing resources could not be found anymore.
This PR makes the deletion more resilient against these cases.
Special notes for your reviewer:
Release note: