-
Notifications
You must be signed in to change notification settings - Fork 390
Fix finalizer removal requeue #1303
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
base: master
Are you sure you want to change the base?
Fix finalizer removal requeue #1303
Conversation
Let syncContent() continue cleaning up VolumeSnapshotContent (i.e. remove its finalizers) after its snapshot has been deleted from the storage backend. It will requeue on all errors. Calling ctrl.updateContentInInformerCache() directly from deleteCSISnapshotOperation() does not requeue the snapshot content on error.
The name suggests it only updates the cache, but it also resyncs the object. There is just only one caller, so remove the function completely.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane 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 |
Again, I can't reproduce the API server hiccup, it requires precise timing. With something like jsafrane@3da05bb, I am able to see: The snapshot deletion works + the external-snapshotter has cleaned VolumeSnapshotContent status:
Finalizer removal failed. With this PR, I can see the snapshotter re-tries periodically:
And eventually it succeeds:
|
What type of PR is this?
/kind bug
What this PR does / why we need it:
The first commit here fixes the linked bug.
Let
syncContent()
continue cleaning up VolumeSnapshotContent (i.e. remove its finalizers) after its snapshot has been deleted from the storage backend.It will requeue on all errors.
Calling
ctrl.updateContentInInformerCache()
directly fromdeleteCSISnapshotOperation()
does not requeue the snapshot content on error.The second commit should be just refactoring,
updateContentInInformerCache
is not really needed now and it has a misleading name.Which issue(s) this PR fixes:
Fixes #1301
Special notes for your reviewer:
Does this PR introduce a user-facing change?: