“No volume ID returned by volume snapshotter for persistent volume” warning is shown for NFS volumes.

[reitermarkus]

What steps did you take and what happened:

Created a backup. It completed successfully, but shows the following warning for an NFS PV:

Warnings:
  Velero:     <none>
  Cluster:   resource: /persistentvolumes name: /my-volume message: /No volume ID returned by volume snapshotter for persistent volume
  Namespaces: <none>

All pods which are using this volume also have the corresponding backup.velero.io/backup-volumes-excludes annotation.

What did you expect to happen:

No warning, since there is no NFS snapshotter and the volume is excluded from backups.

Anything else you would like to add:

Related to https://github.com/vmware-tanzu/velero/issues/7672.

Volume definition:

---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: myvolume
spec:
  capacity:
    storage: 100Ti
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  storageClassName: nfs
  mountOptions:
    - hard
    - nfsvers=4.1
  nfs:
    path: /mypath
    server: myserver

Environment:

• Velero version (use velero version): v1.13.2
• Velero features (use velero client config get features):
• Kubernetes version (use kubectl version): v1.29.6
• Kubernetes installer & version: Talos 1.7.5
• 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.

• :+1: for "I would like to see this bug fixed as soon as possible"
• :-1: for "There are more important bugs to focus on right now"

[ywk253100]

The annotationbackup.velero.io/backup-volumes-excludes is used for file system backup: https://velero.io/docs/v1.14/file-system-backup/#using-the-opt-out-approach

For native snapshot, please define a resource policy to skip the volume: https://velero.io/docs/v1.14/resource-filtering/#resource-policies

[reitermarkus]

@ywk253100, thanks, resource policy was what I was missing.