-
Notifications
You must be signed in to change notification settings - Fork 378
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
Requeue un-ready volume snapshots #958
Requeue un-ready volume snapshots #958
Conversation
ac102fc
to
5d5ca97
Compare
The Trivy error should be fixed by this PR. Please help merge it. Thanks. |
5d5ca97
to
3063863
Compare
/retest |
I think you need to rebase. |
Tests must fail when syncContent() returns success and error was expected.
SnapshotContents with readyToUse: false should be periodically requeued with exp. backoff until the CSI driver confirms the snapshot is ready.
3063863
to
8a29bf5
Compare
Rebased |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane, xing-yang 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Requeue a VolumeSnapshotContent that is
readyToUse: false
with an exp. backoff. This will retry CreateSnapshot CSI call until the snapshot finally getsreadyToUse: true
.Which issue(s) this PR fixes:
Fixes #953
Special notes for your reviewer:
I updated the existing unit tests in the first commit to be able to check when
syncContent
returns no error when an error was expected.Does this PR introduce a user-facing change?: