velero: PV Snapshot not working after upgrading from velero 1.8.0 to 1.13.1

What steps did you take and what happened: Installed latest helm chart 6.0.0 with velero image 1.13.1 and AWS plugin 1.9.1 and CSI plugin 0.7.0.

What did you expect to happen: While creating a backup from CLI using a schedule, PV snapshot backup is not working. It is failing bundle-2024-04-11-16-38-03.tar.gz

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 to velero debug --help

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.)

  • kubectl logs deployment/velero -n velero
  • velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
  • velero backup logs <backupname>
  • velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
  • velero restore logs <restorename>

Anything else you would like to add:

Environment:

  • Velero version (use velero version):
  • Velero features (use velero client config get features):
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • 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”

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 26 (11 by maintainers)

Most upvoted comments

@makarov-roman #7789 is created to cherry-pick the change into release-1.13.

@MoZadro , I created VolumeSnapshotClass for each of my storage class created. And now testing by creating a backup from schedule, i think this will work now but will confirm once backup and restore will be successful.

SC:

NAME                              PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
default-storage-class (default)   ebs.csi.aws.com         Delete          WaitForFirstConsumer   false                  77d
efs-sc-ns      efs.csi.aws.com         Retain          Immediate              false                  48d
gp2                               kubernetes.io/aws-ebs   Delete          WaitForFirstConsumer   false                  204d

Volume Snapshot Class:

csi-aws-vsc-ebs   ebs.csi.aws.com         Delete           11m
csi-aws-vsc-efs   efs.csi.aws.com         Retain           11m
csi-k8s-vsc-ebs   kubernetes.io/aws-ebs   Delete           11m

But I have few queries:

  1. Previously in velero version 1.8.0, we didn’t need to create VolumeSnapshotClass for the SC(provisioners) we had?
  2. Do we need to create VSC for all SC we have in our cluster?
  3. What this label is for "velero.io/csi-volumesnapshot-class: “true”, do I need to give this for each VSC?