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

Failed to cold migrate VM from vCenter without certificate verification

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 2.9.0
    • 2.9.0
    • Guest

      Description of problem:

      Failed to cold migrate VM from vCenter 7 without certificate verification to OCP cluster with preserve static ip, hit this error in conversion pod:

      [0.0] Setting up the source: -i libvirt -ic 
      vpx://administrator%40vsphere.local@10.6.46.170/data/host/10.6.46.28?no_verify=1
       -it vddk mtv-func-rhel8-multi-nicsvirt-v2v:
       error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_ESX: 
      internal error: curl_easy_perform() returned an error: SSL connect error
       (35) : error:1C8000E9:Provider routines::ems not enabled rm -rf -- '/tmp/v2v.73O7Vz' 

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

      MTV 2.9.0 (forklift-fbc-prod-v418:on-pr-16546d253dda4fc8d8b838f0703040f30a985cf0) with CNV 4.18.6 or CNV 4.18.4 (OCP 4.18.17)

      How reproducible:

      100%

      Steps to Reproduce:

      1) Create a cold migration plan: cold-rhel8 to migrate VM: mtv-func-rhel8-multi-nics from vCenter 7 without certificate verification to OCP cluster, mapping the VM network to NAD mybridge network, Mgmt network to NAD mybridge1 network, set the preserve static ip: on

      2) The plan failed in ImageConversion phase

      3) Check the conversion pod log with error below, more details in attached file: cold-rhel8-vm-1204-lc7fv-virt-v2v.log

       [0.0] Setting up the source: -i libvirt -ic 
      vpx://administrator%40vsphere.local@10.6.46.170/data/host/10.6.46.28?no_verify=1
       -it vddk mtv-func-rhel8-multi-nicsvirt-v2v:
       error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_ESX: 
      internal error: curl_easy_perform() returned an error: SSL connect error
       (35) : error:1C8000E9:Provider routines::ems not enabled rm -rf -- '/tmp/v2v.73O7Vz' 

      Actual results:

      Step2: The plan is failed

      Expected results:

      Step2: The plan is succeeded

              mnecas@redhat.com Martin Necas
              chhu@redhat.com Chenli Hu
              Chenli Hu Chenli Hu
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: