-
Bug
-
Resolution: Done
-
Normal
-
OADP 1.1.0
Description of problem: VSB/VSR pods are not getting terminated when VSR/VSB is deleted.
Thus, when the VSB/VSR is not completed, as in https://issues.redhat.com/browse/OADP-647 scenario, the pods may still remain on the namespace, although the the VSB/VSR was removed, or the namespace which the VSB/VSR lives was removed.
Version-Release number of selected component (if applicable):
1.1.0-50
How reproducible: 100%
Steps to Reproduce:
1. Create a backup using DataMover
2. When the vsb/vsr pod is running, delete the VSB/VSR from the namespace
3. Check the pods status and note that they are still running
Actual results:
[mperetz@mperetz oadp-e2e-qe]$ oc get vsb -A -o yaml apiVersion: v1 items: - apiVersion: datamover.oadp.openshift.io/v1alpha1 kind: VolumeSnapshotBackup metadata: creationTimestamp: "2022-07-31T14:01:13Z" generation: 1 labels: velero.io/backup-name: mysql-d1fdaa66-10d8-11ed-8cba-902e163f806c name: vsb-velero-mysql-pqpws namespace: mysql-persistent resourceVersion: "785773" uid: 8e86e6d9-de7a-4692-b8fd-605fc6b5f131 spec: protectedNamespace: openshift-adp resticSecretRef: name: ts-dpa-1-volsync-restic volumeSnapshotContent: name: snapcontent-f482bc42-7d28-4265-aad9-3bb619544300 status: resticrepository: s3:http://s3.openshift-storage.svc.cluster.local:80/oadpbucket125989/openshift-adp/snapcontent-f482bc42-7d28-4265-aad9-3bb619544300-pvc sourcePVCData: name: mysql size: 2Gi storageClassName: ocs-storagecluster-ceph-rbd volumeSnapshotClassName: example-snapclass kind: List metadata: resourceVersion: "" selfLink: "" [mperetz@mperetz oadp-e2e-qe]$ oc get pods -n openshift-adp NAME READY STATUS RESTARTS AGE openshift-adp-controller-manager-786ff7bd8-mbmjs 1/1 Running 0 3h18m restic-jsj5x 1/1 Running 0 4m6s restic-nmzj8 1/1 Running 0 4m6s restic-p9lvg 1/1 Running 0 4m6s velero-5889c69945-fbvm7 1/1 Running 0 4m6s volume-snapshot-mover-64cdcf4b97-bffft 1/1 Running 0 4m6s vsb-velero-mysql-dxxlr-pod 1/1 Terminating 0 31m vsb-velero-mysql-pqpws-pod 0/1 ContainerCreating 0 4s [mperetz@mperetz oadp-e2e-qe]$ oc delete vsb -A --all volumesnapshotbackup.datamover.oadp.openshift.io "vsb-velero-mysql-pqpws" deleted [mperetz@mperetz oadp-e2e-qe]$ oc get pods -n openshift-adp NAME READY STATUS RESTARTS AGE openshift-adp-controller-manager-786ff7bd8-mbmjs 1/1 Running 0 3h18m restic-jsj5x 1/1 Running 0 4m23s restic-nmzj8 1/1 Running 0 4m23s restic-p9lvg 1/1 Running 0 4m23s velero-5889c69945-fbvm7 1/1 Running 0 4m23s volume-snapshot-mover-64cdcf4b97-bffft 1/1 Running 0 4m23s vsb-velero-mysql-pqpws-pod 1/1 Running 0 21s
Expected results: would expect the VSB/VSR pod to terminate, otherwise the user would need to delete those pods manually in case of stuck VSB/VSRs
- links to