Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-3659

To many bounded "ova-store-pvc-*" PVCs left after migrating VM from ova file to OCP cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 2.10.0
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False

      Description of problem:

      Migrate VM from OVA file to target OCP cluster, the plan executed successfully. The VM is running on target cluster, there are many bounded "ova-store-pvc-*" PVCs left in cluster, the VM yaml file is without these PVCs.

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

      MTV 2.10.0-26 with CNV 4.20.0

      How reproducible:

      Always

      Steps to Reproduce:

      1) Add the feature flag in the forklift-controller: `feature_ova_appliance_management: 'true'`

      2) Create a ova provider: ova-chhu with "applianceManagement: 'true'", it has VMs: mtv-rhel8-warm-2disks2nics

      3) Create migration plan: copy-of-ova-chhu-rhel8 to migrate VM:  mtv-rhel8-warm-2disks2nics from ova provider to OCP cluster, plan executed successfully.

      4) Check the PVC, beside the 2 PVCs for 2 disks, there are 5 "ova-store-pvc-ova-chhu-*" Bound PVCs left. [In another plan, there are 13 "ova-store-pvc-*" Bound PVCs left after migration]

      oc get pvc|grep rhel8
      copy-of-ova-chhu-rhel8-7e9f6600dccdb1cc155d8b43622200f050emhcvp   Bound    pvc-98c4ccaf-bc97-4ce7-b57c-d3410ff9128f             16Gi       RWX            ocs-storagecluster-ceph-rbd   <unset>                 11h
      copy-of-ova-chhu-rhel8-7e9f6600dccdb1cc155d8b43622200f050es867q   Bound    pvc-dfa1f805-7764-4d0d-97a1-d409424746bc             12Gi       RWX            ocs-storagecluster-ceph-rbd   <unset>                 11h
      ova-store-pvc-ova-chhu-copy-of-ova-chhu-rhel8-d2l4z               Bound    ova-store-pv-ova-chhu-copy-of-ova-chhu-rhel8-zfzfm   1Gi        ROX                                          <unset>                 11h
      ova-store-pvc-ova-chhu-copy-of-ova-chhu-rhel8-m8cdg               Bound    ova-store-pv-ova-chhu-copy-of-ova-chhu-rhel8-2gt7r   1Gi        ROX                                          <unset>                 11h
      ova-store-pvc-ova-chhu-copy-of-ova-chhu-rhel8-p5ldc               Bound    ova-store-pv-ova-chhu-copy-of-ova-chhu-rhel8-ccmd2   1Gi        ROX                                          <unset>                 11h
      ova-store-pvc-ova-chhu-copy-of-ova-chhu-rhel8-qqpcw               Bound    ova-store-pv-ova-chhu-copy-of-ova-chhu-rhel8-htlmx   1Gi        ROX                                          <unset>                 11h
      ova-store-pvc-ova-chhu-copy-of-ova-chhu-rhel8-zjvxx               Bound    ova-store-pv-ova-chhu-copy-of-ova-chhu-rhel8-829sf   1Gi        ROX                                          <unset>                 11h

      5) Check on target cluster, the VM yaml file with 2 disks PVCs, the ova-store-pvc-*" Bound PVCs are not used in VM

      6) Create a ova provider without "applianceManagement: 'true'", create a plan to migrate VM: win2022test, plan executed successfully, check on target cluster after migration, it also have 4 Bounded ova-store-pvc-** left on cluster.

      Actual results:

      In step4: There are 5 "ova-store-pvc-ova-chhu-*" Bound PVCs on target cluster, 
                in another plan 13 "ova-store-pvc-ova-chhu-*" Bound PVCs left on target cluster

      Expected results:

      In step4: No "ova-store-pvc-ova-chhu-*" Bound PVCs left on target cluster

      Additional info:

       

              slucidi@redhat.com Samuel Lucidi
              chhu@redhat.com Chenli Hu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: