-
Notifications
You must be signed in to change notification settings - Fork 391
Retain volumesnapshot-being-created annotation until readyToUse=true #1283
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?
Retain volumesnapshot-being-created annotation until readyToUse=true #1283
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pwschuurman The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @sunnylovestiramisu |
/lgtm Thanks! |
04ad286
to
ad35797
Compare
New changes are detected. LGTM label has been removed. |
content, err = ctrl.removeAnnVolumeSnapshotBeingCreated(content) | ||
if err != nil { | ||
return content, fmt.Errorf("failed to remove VolumeSnapshotBeingCreated annotation on the content %s: %q", content.Name, err) | ||
if contentIsReady(content) { |
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.
As described in the comments, the annotation is only needed before the snapshot is cut on the storage system. After the snapshot is cut, a snapshot id will be returned and can be used to identify the snapshot on the storage system (if user chooses to delete the snapshot).
I don't see why we have to wait until the snapshot is post processed and ready to use set to true.
What type of PR is this?
/kind bug
What this PR does / why we need it:
In
createSnapshotWrapper()
, thesnapshot.storage.kubernetes.io/volumesnapshot-being-created
annotation is removed even if the snapshot is not marked asreadyToUse
true. This is inconsistent with the same logic insyncContent()
where we only remove the annotation if the snapshot content is ready:external-snapshotter/pkg/sidecar-controller/snapshot_controller.go
Line 102 in 59d7297
Which issue(s) this PR fixes:
This change may reduce symptoms seen in #1282. However this does not fix the root cause of immedate vs. scheduled exponential backoff requeuing.
Special notes for your reviewer:
Does this PR introduce a user-facing change?: