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

No interface related settings in VM yaml file after migrating VM from ova file to OCP cluster

XMLWordPrintable

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

      None

      Show
      None
    • False

      Description of problem:

      Migrate VM with 2 interfaces with dhcp settings from ova provider to OCP cluster, map "VM Network" to default network, "Mgmt Network" to mtv-test/vlan-br-eno8043 network, plan executed successfully, check on target cluster after migration, no interface related settings in VM yaml file and only 1 default interface with pod network in VM.
      
      Notice: 
      Migrate another VM mtv-rhel8-warm-2disks2nics from the same provider: ova-chhu, after migration, check on the target cluster: the VM yaml file with 2 interface settings and VM has 2 interface with correct ip address
      
      Not sure if the interface settings disappear only happened to VM with only DHCP settings,
      And it also may caused by the VM name changed from name: Auto-esx8.0-win2019-efi-with-extra-online-disks to newName: auto-esx8.0-win2019-efi-with-extra-online-disks

      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: Auto-esx8.0-win2019-efi-with-extra-online-disks and mtv-rhel8-warm-2disks2nics

      3) Create migration plan: ova-chhu-win2019-vlan to migrate VM: Auto-esx8.0-win2019-efi-with-extra-online-disks (2 interfaces with dhcp settings) from ova provider to OCP cluster, with networkmap as below, more details in files: plan-ova-chhu-win2019-vlan-yaml, networkmap-ova-chhu-btbhd-yaml

      4) The plan executed successfully, VM is running on target cluster

      5) Check the VM yaml file without the interface setting, more details in file: vm-auto-esx8.0-win2019-efi-with-extra-online-disks-yaml

      6) Login to VM, VM with only 1 interface with Pod network

      Actual results:

      In step5,6: The VM yaml file without interface settings, only 1 interface in VM

      Expected results:

      In step5,6: The VM yaml file with 2 interface settings, VM has 2 interfaces

      Additional info:

      Migrate another VM mtv-rhel8-warm-2disks2nics from the same provider: ova-chhu, after migration, check on the target cluster: the VM yaml file with 2 interface settings and VM has 2 interface with correct ip address, more details as below

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

                Created:
                Updated: