-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
Not Selected
-
ToDo
-
-
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
None
This issue tracks the upstream Velero GitHub issue #7233 which is part of the Velero v1.18 milestone.
Description
Backup namespace contains PVCs which not in used by any pod, then got PartiallyFailed result.
Example scenario:
k get pvc -n azure-csi-test NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE nginx-logs-e2e-1 Bound pvc-e4dda753-8c88-4194-93b5-959a01be1de4 1Gi RWO managed-csi 16h nginx-logs-e2e-2 Pending managed-csi 16h nginx-logs-e2e-3 Pending managed-csi 16h nginx-logs-e2e-4 Pending managed-csi 16h nginx-logs-e2e-5 Pending managed-csi 16h
This results in PartiallyFailed backup with errors like:
Error backing up item error: error executing custom action (groupResource=persistentvolumeclaims, namespace=azure-csi-test, name=nginx-logs-e2e-2): rpc error: code = Unknown desc = PVC azure-csi-test/nginx-logs-e2e-2 has no volume backing this claim
The proposed solution is to introduce ability to skip unbound PVCs through new volume policy actions https://velero.io/docs/main/resource-filtering/#supported-volumepolicy-actions
Upstream Details
- GitHub Issue: https://github.com/vmware-tanzu/velero/issues/7233
- Status: Open (reopened)
- Assignee: kaovilai
- Labels: 2024 Q1 reviewed, target/1.16.3, target/v1.17.1, Reviewed Q3 2025
- Created: 2023-12-20T02:13:04Z
- Updated: 2025-09-24T10:49:00Z
This is related to https://issues.redhat.com/browse/OADP-6428.