Backup is marked as waitingForPluginOperationsPartiallyfailed when VolumeSnapshotContent has an error #7356
Comments
|
Proposed solution in draft PR: vmware-tanzu/velero-plugin-for-csi#226 This is inline with what we do for VolumeSnapshot backup plugin |
reasonerjt
added
Needs triage
|
I'm having the same problem: To Backup (manually - usually via schedule): |
|
i had the same problem logvelero version : 1.11 |
|
@shubham-pampattiwar This issue is currently target for 1.14.1. Are you planning to fix it there? If not, let's remove it from 1.14.1. |
|
@Lyndon-Li will have to re-think the earlier proposed solution for this as the code flow has changed because of updates to the progress method of VSC async action operation as well as merging of csi plugin to velero core. yes I would like to try to solve this for 1.14.1 but will have to re-think, maybe will have to add the re-try on temporary error mechanism in WaitUntilVSCHandleIsReady function in the current code flow. Any thoughts on this ? |
3 tasks
|
Draft PR against latest Velero for proposed solution: #8023 |
|
Closing this issue as we are currently not seeing this behavior in our testing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps did you take and what happened:
We have been seeing this issue recently, if any of the VolumeSnapshotContent CR has an error related to removing VolumeSnapshotBeingCreated annotation in that case it moves backup to WaitingForPluginOperationsPartiallyFailed phase. Due to this most of the CSI/NativeDataMover backups are failing recently.
Here you can see that backup is marked
waitingForPluginOperationsPartiallyfailedin only 3mins after the startIntermittent(It happens when VolumeSnapshotContent CR has error related to removing annotation)
What did you expect to happen:
Backup to not fail on temporary VSC errors. CSI plugin should wait at least for the specified csiSnapshotTimeout.
The following information will help us better understand what's going on:
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>to generate the support bundle, and attach to this issue, more options please refer tovelero debug --helpIf you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velerovelero backup describe <backupname>orkubectl get backup/<backupname> -n velero -o yamlvelero backup logs <backupname>velero restore describe <restorename>orkubectl get restore/<restorename> -n velero -o yamlvelero restore logs <restorename>Anything else you would like to add:
Environment:
velero version):velero client config get features):kubectl version):/etc/os-release):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: