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

Fail to create vCenter provider if don't skip certificate validation on MTV

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 2.10.1
    • Controller
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • True

      Description of problem:

      Fail to create vCenter provider if don't skip certificate validation on MTV

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

      MTV:2.10.1

      How reproducible:

      100 %
      

      Steps to Reproduce:

      1.Create a vcenter provider and don't skip certificate validation on MTV 
      3.The provider can't be created with below error 
      failed to create a secure TLS connection: tls: failed to verify certificate: x509: cannot validate certificate for 10.73.212.179 because it doesn't contain any IP SANs. To troubleshoot, check the Forklift controller pod logs.

      Actual results:

      As above description

      Expected results:

      Fix the bug

      Additional info:

      1. Can create vcenter provider if skip certificate validation on MTV2.10.1

      2. Can't reproduce the bug on RHEL10.1

       

      # virsh -c vpx://root@bootp-73-213-134.lab.eng.pek2.redhat.com/data/cluster/10.73.212.36
      Enter root's password for bootp-73-213-134.lab.eng.pek2.redhat.com: 
      Welcome to virsh, the virtualization interactive terminal.
      Type:  'help' for help with commands
             'quit' to quit
      virsh # 
      

        1. ca_cert_got_on_mtv.txt
          2 kB
          Ming Xie
        2. skip-certificate.png
          55 kB
          Ming Xie
        3. verify-certificate.png
          79 kB
          Ming Xie

              rh-ee-ehazan Elad Hazan
              mxie@redhat.com Ming Xie
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: