@shubham-pampattiwar
The issue is about a mismatching behavior to check --snapshot-volume flag by volume policy.

However, I discussed further with @reasonerjt for this issue, we think volume policy may not need to respect --snapshot-volume flag, since volume policy always take the preference, if the condition is met which means volume policy voting the snapshot action, the backup should go with snapshot action not matter how snapshot-volume is set.
So we may need to change the existing code of Velero where snapshot-volume is being checked.

@Lyndon-Li I think not respecting snapshotVolmes as true may not be the best idea here. The CSI plugin depends on this value to perform snapshots:

@Lyndon-Li I think not respecting snapshotVolmes as true may not be the best idea here. The CSI plugin depends on this value to perform snapshots:

velero/pkg/backup/actions/csi/pvc_action.go

Line 68 in 0d85a64

if boolptr.IsSetToFalse(backup.Spec.SnapshotVolumes) {

@shubham-pampattiwar Actually the idea we discussed yesterday is that once the volume policy chooses snapshot for a volume, any other places (including CSI plugin) should not check for the SnapshotVolumes again. This introduces more changes than the code for volume policy but it makes things more clear.

Created a PR for this issue: #7786

Fixed by #7794