-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add missing requeue to Datacenter decommission #322
Conversation
@burmanm can you please create an issue for this? |
@@ -70,6 +70,8 @@ func (rc *ReconciliationContext) ProcessDeletion() result.ReconcileResult { | |||
// Exiting to let other parts of the process take care of the decommission | |||
return result.Continue() | |||
} | |||
// How could we have pods if we've decommissioned everything? | |||
return result.RequeueSoon(5) |
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.
Are you adding the requeue here to handle the scenario where len(dcs) == 1
?
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.
Why would we requeue in that case? If len(dcs) == 1, we go and delete the DC.
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.
It's not obvious to me why the need for the requeue here. Can you explain?
* Add requeue if we still have pods although decommission has succeeded * CHANGELOG (cherry picked from commit addd528)
What this PR does:
Decommissioning datacenter is missing a requeue after scaling down is done, but the pods haven't been removed yet. This can cause the operator to remove PVCs before Cassandra has properly shutdown (it has 30s wait after decommission).
Which issue(s) this PR fixes:
Fixes #323
Checklist