-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
2.10.2
After running a migration with Storage Offload, the prime PVC remains stuck in the Terminating state, even after the xcopy operation completes successfully / fails
This blocks proper cleanup and may result in leftover resourcess
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-powerstore.dellemc.com volume.kubernetes.io/storage-provisioner: csi-powerstore.dellemc.com creationTimestamp: "2025-12-07T20:20:47Z" deletionGracePeriodSeconds: 0 deletionTimestamp: "2025-12-07T20:31:39Z" finalizers: - kubernetes.io/pvc-protection name: prime-2d45328d-7c42-4c0e-aea9-4b0779f2ce60 namespace: default resourceVersion: "85215023" uid: 01a0e7d7-890c-4301-a31c-ed829f4e3284 spec: accessModes: - ReadWriteOnce resources: requests: storage: 25Gi storageClassName: powerstore-xfs volumeMode: Block volumeName: csivol-01a0e7d789 status: phase: Lost
oc get pvc -A|grep csivol-0c7ffc130f powerstore prime-6824a627-f02e-4190-93ac-59e449dfb0e7 Terminating csivol-0c7ffc130f 0 powerstore-config <unset> 18m powerstore test-rhel-disk-0-2744f588 Bound csivol-0c7ffc130f 50Gi RWX powerstore-config <unset> 18m