-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
4
-
False
-
-
False
-
ToDo
-
-
-
0
-
0.000
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
Description of problem:
VolumeSnapshotContents are left out in the cluster even after the backup is removed. This issue only happens when vsclass has deletionPolicy set as Retain.
Upstream tracking issue:-
https://github.com/vmware-tanzu/velero/issues/6786
Version-Release number of selected component (if applicable):
Velero 1.12.0
How reproducible:
Always
Steps to Reproduce:
1. Create VSclass resource with DeletionPolicy set as Retain.
2. Create a backup with native dataMover.
$ oc get backup test-backup -o yaml
apiVersion: velero.io/v1
kind: Backup
metadata:
annotations:
velero.io/resource-timeout: 10m0s
velero.io/source-cluster-k8s-gitversion: v1.26.7+0ef5eae
velero.io/source-cluster-k8s-major-version: "1"
velero.io/source-cluster-k8s-minor-version: "26"
creationTimestamp: "2023-09-07T11:22:11Z"
generation: 9
labels:
velero.io/storage-location: ts-dpa-1
name: test-backup
namespace: openshift-adp
resourceVersion: "159157"
uid: c0a64106-724f-4453-ab5c-df6b8a92e5c9
spec:
csiSnapshotTimeout: 10m0s
defaultVolumesToFsBackup: false
includedNamespaces:
- ocp-django
itemOperationTimeout: 4h0m0s
snapshotMoveData: true
storageLocation: ts-dpa-1
ttl: 720h0m0s
status:
backupItemOperationsAttempted: 1
backupItemOperationsCompleted: 1
completionTimestamp: "2023-09-07T11:23:42Z"
expiration: "2023-10-07T11:22:11Z"
formatVersion: 1.1.0
phase: Completed
progress:
itemsBackedUp: 96
totalItems: 96
startTimestamp: "2023-09-07T11:22:11Z"
version: 1
Actual results:
VolumeSnapshotContent resources are left out in the cluster.
Expected results:
VolumesnapshotContent should get removed before backup is marked as completed.
Additional info:
