Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-42509

MTV - imported VMWare fails to cleanup Lost pvc's and delete vm fails to delete pvc's

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • CNV v4.16.0
    • CNV Storage
    • None
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • ---
    • ---
    • Medium
    • No

      Description of problem:

      Importing VMware VM with MTV to CNV cluster. On completion there is one bound pvc and one Lost PVC which was not cleaned up. Then deleting the VM succeeds but the the bound pvc  is stuck terminating and the lost pvc is not removed.

      Version-Release number of selected component (if applicable):

      Testing with the following code:
      
      oc version
      
      Client Version: 4.16.0-ec.5
      
      Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
      
      Server Version: 4.16.0-ec.5
      
      Kubernetes Version: v1.29.2+258f1d5
      
      oc get csv -n openshift-cnv
      
      NAME                                       DISPLAY                      
         VERSION             REPLACES                                   PHASE
      
      kubevirt-hyperconverged-operator.v4.16.0   OpenShift Virtualization      
        4.16.0              kubevirt-hyperconverged-operator.v4.15.2   
      Succeeded
      
      odr-cluster-operator.v4.16.0-106.stable    Openshift DR Cluster Operator
         4.16.0-106.stable   odr-cluster-operator.v4.16.0-94.stable     
      Succeeded
      
      openshift-gitops-operator.v1.12.2          Red Hat OpenShift GitOps      
        1.12.2              openshift-gitops-operator.v1.12.1         
       Succeeded
      
      volsync-product.v0.9.1                     VolSync                      
         0.9.1               volsync-product.v0.9.0                     
      Succeeded

      How reproducible:

      100%

      Steps to Reproduce:

      Steps to reproduce:
      1. Import VMware Rhel8 VM with MTV to Openshift Virtualization cluster
      During import a datavolume is created, one bound pvc and one 'lost' pvc
      During import:
      oc get dv -n vmware-rhel8-sanity2
      NAME                                  PHASE       PROGRESS   RESTARTS   AGE
      Succeeded   100.0%                2m6s
      oc get pvc -n vmware-rhel8-sanity2
      NAME                                         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                                 VOLUMEATTRIBUTESCLASS   AGE
      prime-0e18dce5-f8e1-4f0a-9b1d-d348692b34eb   Lost     pvc-ebbc7fe6-c817-4517-b528-588b7ebd0eea   0                         ocs-storagecluster-ceph-rbd-virtualization   <unset>                 5m6s
      vmware-rhel8-sanity2-vm-23154-pl7wj          Bound    pvc-ebbc7fe6-c817-4517-b528-588b7ebd0eea   12Gi       RWX            ocs-storagecluster-ceph-rbd-virtualization   <unset>                 5m6s
       
      2. On completion of the MTV import the vm is created, the datavolume was deleted and the 2 pvc's remained:
      oc get vm -n vmware-rhel8-sanity2
      NAME               AGE     STATUS    READY
      mtv-rhel8-sanity   3h10m   Stopped   False
      oc get dv -n vmware-rhel8-sanity2
      No resources found in vmware-rhel8-sanity2 namespace.
      oc get pvc -n vmware-rhel8-sanity2
      NAME                                         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                                 VOLUMEATTRIBUTESCLASS   AGE
      prime-0e18dce5-f8e1-4f0a-9b1d-d348692b34eb   Lost     pvc-ebbc7fe6-c817-4517-b528-588b7ebd0eea   0                         ocs-storagecluster-ceph-rbd-virtualization   <unset>                 3h32m
      vmware-rhel8-sanity2-vm-23154-pl7wj          Bound    pvc-ebbc7fe6-c817-4517-b528-588b7ebd0eea   12Gi       RWX            ocs-storagecluster-ceph-rbd-virtualization   <unset>                 3h32m
       
      3. Deleting the VM, the vm is deleted, the bound pvc is stuck 'terminating' and the lost pvc remains:
      oc get vm -n vmware-rhel8-sanity2
      No resources found in vmware-rhel8-sanity2 namespace.
      oc get dv -n vmware-rhel8-sanity2
      No resources found in vmware-rhel8-sanity2 namespace.
      oc get pvc -n vmware-rhel8-sanity2
      NAME                                         STATUS        VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                                 VOLUMEATTRIBUTESCLASS   AGE
      prime-0e18dce5-f8e1-4f0a-9b1d-d348692b34eb   Lost          pvc-ebbc7fe6-c817-4517-b528-588b7ebd0eea   0                         ocs-storagecluster-ceph-rbd-virtualization   <unset>                 6h29m
      vmware-rhel8-sanity2-vm-23154-pl7wj          Terminating   pvc-ebbc7fe6-c817-4517-b528-588b7ebd0eea   12Gi       RWX            ocs-storagecluster-ceph-rbd-virtualization   <unset>                 6h29m

      Actual results:

      VM import with MTV did not clean up the lost pvcs and deleting the vm did not leaves the bound pvc stuck terminating

      Expected results:

      The lost pvcs should be cleaned up after importing and deleting the vm should delete the bound pvc

      Additional info:

       

            ahadas@redhat.com Arik Hadas
            kgoldbla Kevin Alon Goldblatt
            Kevin Alon Goldblatt Kevin Alon Goldblatt
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: