Creating backup using `VolumeGroupSnapshot` failed

What steps did you take and what happened: I tried to create a VolumeGroupSnapshot (VGS) of two PVCs in the same namespace. I added the required velero.io/volume-group: xxx label. The corresponding VGS got created and was ready to use. Same for the VGSC, VS and VSC. The difference that I noticed is that the V(G)S(C) have the namespace of the service (xxx) and not velero like for normal snapshot backups. Then after 10 min it timed out with the following error:

time="2026-03-23T14:02:31Z" level=error msg="Error backing up item" backup=velero/xxx-20260323135228 error="error executing custom action (groupResource=persistentvolumeclaims, namespace=xxx, name=xxx-storage): rpc error: code = Unknown desc = timeout waiting for VolumeSnapshots to have status created via VolumeGroupSnapshot velero-xxx-2gksg: timeout waiting for VolumeSnapshots associated with VGS velero-xxx-2gksg: client rate limiter Wait returned an error: context deadline exceeded" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/backup/item_backupper.go:397" error.function="github.com/vmware-tanzu/velero/pkg/backup.(*itemBackupper).executeActions" logSource="pkg/backup/backup.go:929" name=xxx-storage

What did you expect to happen: That VGS backups (+ Data Mover) work.

Environment:

• Velero version (use velero version): v1.18.0
• Velero features (use velero client config get features): features: <NOT SET>
• Kubernetes version (use kubectl version): v1.35.3
• Cloud provider or hardware configuration: Using Piraeus
• OS (e.g. from /etc/os-release): TalosOS

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"