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

[cnv-4.14] New migration overwrites older VMIM data

XMLWordPrintable

    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • CNV v4.14.11.rhel9-41
    • Hide

      When a new migration is executing, it changes migration data for all the vmim objects with the same vmi name, not only for the relevant vmim.

      For example, all pass migrations have the same uid:
      [root@e26-h06-000-r640 ~]# oc get vmim | grep fedora-8 | awk '{print $1}' | xargs -I file sh -c 'echo file; oc get vmim file -o yaml| grep -E "migrationUid"'
      kubevirt-evacuation-5c4sj
          migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160
      kubevirt-evacuation-hq9lj
          migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160
      kubevirt-evacuation-ld5tx
          migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160
      kubevirt-workload-update-mqwvm
          migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160
      kubevirt-workload-update-pnlvf
          migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160

      Show
      When a new migration is executing, it changes migration data for all the vmim objects with the same vmi name, not only for the relevant vmim. For example, all pass migrations have the same uid: [root@e26-h06-000-r640 ~] # oc get vmim | grep fedora-8 | awk '{print $1}' | xargs -I file sh -c 'echo file; oc get vmim file -o yaml| grep -E "migrationUid"' kubevirt-evacuation-5c4sj     migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160 kubevirt-evacuation-hq9lj     migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160 kubevirt-evacuation-ld5tx     migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160 kubevirt-workload-update-mqwvm     migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160 kubevirt-workload-update-pnlvf     migrationUid: 4cda42e4-46ec-40d3-a8bf-c6abedfc9160
    • ---
    • ---
    • Critical
    • None

      Description of problem:

      When a new migration is executing, it changes migration data for all the vmim objects with the same vmi name, not only for the relevant vmim.

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

      CNV 4.15.4

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create VMS
2. Migrate VMS several times 
3. See that all VMIM migration data changes, including older ones

      Actual results:

       

      Expected results:

       

      Additional info:

       

        1. kubevirt-evacuation-5c4sj.yaml
          2 kB
        2. kubevirt-evacuation-hq9lj.yaml
          2 kB
        3. kubevirt-evacuation-ld5tx.yaml
          2 kB
        4. kubevirt-migrate-vm-5ks88-afterFirstMigration.yaml
          2 kB
        5. kubevirt-migrate-vm-5ks88-afterMigration2.yaml
          2 kB
        6. kubevirt-migrate-vm-5ks88-afterMigration3.yaml
          2 kB
        7. kubevirt-migrate-vm-6kggb-afterMigration3.yaml
          2 kB
        8. kubevirt-migrate-vm-zfr5d-afterMigration2.yaml
          2 kB
        9. kubevirt-migrate-vm-zfr5d-afterMigration3.yaml
          2 kB
        10. kubevirt-workload-update-mqwvm.yaml
          2 kB
        11. kubevirt-workload-update-pnlvf.yaml
          2 kB
        12. must-gather.local.8948285524674220215.tar.gz
          94.23 MB

              rh-ee-dsionov Daniel Sionov
              guchen11 Guy Chen
              Kedar Bidarkar Kedar Bidarkar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: