velero backup has an warning 'No volume ID returned by volume snapshotter for persistent volume'

[bhavyashree231]

What steps did you take and what happened: velero backup was taken with respect to the specific namespace which in turn had few of the pod volumes excluded using annotations. backup was completed successfully with the warnings as below

What did you expect to happen: successful backup without warning & errors since they are already excluded.

Anything else you would like to add:

Environment:

• Velero version (use velero version): 1.14.0
• Velero features (use velero client config get features): NA
• Kubernetes version (use kubectl version): 1.28 & 1.30
• Kubernetes installer & version: GKE
• Cloud provider or hardware configuration: GCP
• OS (e.g. from /etc/os-release): NA

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"

[Lyndon-Li]

It is the expected behavior that the native snapshotter takes over the volume backup if no other method is selected, and if the native snapshotter cannot handle the volume, it gives a warning.

For whether it is expected for the native snapshotter to handle the volume, you need to check you backup options which selects the backup method, i.e., fs-backup, CSI snapshot, CSI snapshot data movement, etc.

[kaovilai]

pod volumes excluded using annotations.

The annotations you used are only processed for file-system-backup currently.

Like Lyndon said, if your environment allows for native snapshotter to take over (perhaps you have created a VolumeSnapshotLocation)

It is possible to exclude volumes from being backed up using the backup.velero.io/backup-volumes-excludes annotation on the pod.

is only mentioned in File System Backup documentations. It is also applicable to FSBackups specified via Volume Policy

[ithesadson]

@bhavyashree231 I recently had such a problem and I'm sharing the url. Maybe it might help you. Issue #7990

[github-actions[bot]]

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.