Retain volumesnapshot-being-created annotation until readyToUse=true #1283
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?: