You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a schedule with Velero CSI snapshot with data mover enabled.
Attempt to perform a backup using the created schedule.
What did you expect to happen:
The backup process should complete successfully without encountering any errors.
I encountered a similar issue as described here: Issue 7068. I tried to resolve it by increasing memory resources, but unfortunately, it didn't solve the problem for me.
If 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.)
Cloud provider or hardware configuration: DigitalOcean Cluster, s3 bucket
OS (e.g. from /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.
👍 for "I would like to see this bug fixed as soon as possible"
👎 for "There are more important bugs to focus on right now"
The text was updated successfully, but these errors were encountered:
nknoii
changed the title
Error Exposing Snapshot with Velero CSI Snapshot Schedule
Error exposing snapshot with velero CSI snapshot schedule
Mar 18, 2024
This looks more like #6852. @nknoii Is this a consistent problem in your env? If so, please collect CSI external-snapshotter logs according to this comment after the error happens, and then collect Velero log bundle during the same period of time
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.
What steps did you take and what happened:
What did you expect to happen:
The backup process should complete successfully without encountering any errors.
I encountered a similar issue as described here: Issue 7068. I tried to resolve it by increasing memory resources, but unfortunately, it didn't solve the problem for me.
If 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.)
$ velero backup describe database-backup --details
$ velero backup logs database-backup
https://gist.github.com/nknoii/c36367fadb9bdccd51c3e0bbca935904
Anything else you would like to add:
Environment:
6.0.0 (Helm chart)
): App Version: 1.13.0, velero-plugin-for-aws:v1.9.0, velero-plugin-for-csi:v0.7.0/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: