-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
2.6.3
-
None
-
None
-
False
-
None
-
False
-
-
-
Low
After a successful cold migration, the populator pod is not cleaned up and leaves a Lost PVC similar to MTV-1095
Versions:
OCP 4.15.11
OCV 4.15.2
MTV 2.6.3
$ oc get pods,pvc -A NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE default persistentvolumeclaim/prime-38aeb8f1-c24a-4d3f-95b1-16354f38f30b Lost pvc-4b8ebb00-8567-4b99-9297-f374c94b0036 0 trident-nfs-svm <invalid> NAMESPACE NAME READY STATUS RESTARTS AGE default pod/populate-38aeb8f1-c24a-4d3f-95b1-16354f38f30b 0/1 Completed 0 <invalid>
$ oc get pvc/prime-38aeb8f1-c24a-4d3f-95b1-16354f38f30b -n default -o yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" pv.kubernetes.io/bound-by-controller: "yes" volume.beta.kubernetes.io/storage-provisioner: csi.trident.netapp.io volume.kubernetes.io/storage-provisioner: csi.trident.netapp.io creationTimestamp: "2024-07-17T19:43:49Z" deletionGracePeriodSeconds: 0 deletionTimestamp: "2024-07-17T19:45:24Z" finalizers: - kubernetes.io/pvc-protection name: prime-38aeb8f1-c24a-4d3f-95b1-16354f38f30b namespace: default resourceVersion: "69160602" uid: 4b8ebb00-8567-4b99-9297-f374c94b0036 spec: accessModes: - ReadWriteMany resources: requests: storage: "298261617778" storageClassName: trident-nfs-svm volumeMode: Filesystem volumeName: pvc-4b8ebb00-8567-4b99-9297-f374c94b0036 status: phase: Lost
The above pvc is still "used" by the populate-* pod, which didn't get cleaned up.
$ oc get pod/populate-38aeb8f1-c24a-4d3f-95b1-16354f38f30b -n default -o yaml | yq '.spec.volumes' - name: target persistentVolumeClaim: claimName: prime-38aeb8f1-c24a-4d3f-95b1-16354f38f30b
- is related to
-
-
- Closed
-