I m trying to get VM Import for VMWare working following the rancher-users #harvester

Title

rapid-flag-87720

03/03/2023, 7:40 PM

I'm trying to get VM Import for VMWare working following the doc at https://docs.harvesterhci.io/v1.1/advanced/vmimport/ but I get this after setting up the source

harvester-management:/home/rancher # kubectl get vmwaresource.migration
NAME    STATUS
vcsim   clusterNotReady

salmon-city-57654

03/06/2023, 8:14 AM

Hi @rapid-flag-87720, could you verify your source configuration and vsphere source status? Thanks!

rapid-flag-87720

03/08/2023, 5:50 PM

Hi @salmon-city-57654. Here's what I have:

apiVersion: v1
kind: Secret
metadata:
  name: vsphere-credentials
  namespace: default
stringData:
  "username": "xxxxxx"
  "password": "xxxxxx"

apiVersion: <http://migration.harvesterhci.io/v1beta1|migration.harvesterhci.io/v1beta1>
kind: VmwareSource
metadata:
  name: vcsim
  namespace: default
spec:
  endpoint: "<http://100.80.243.158/sdk>"
  dc: "DCO"
  credentials:
    name: vsphere-credentials
    namespace: default

I tested ping from both harvester hosts I have to vsphere IP and the other way around as well, it works both ways with the correct nics and interfaces.

I tried govc as well and got the following error:

govc: Post "<https://100.80.243.158/sdk>": x509: cannot validate certificate for 100.80.243.158 because it doesn't contain any IP SANs

Not sure if harvester can skip verify in that case or not. It doesn't appear in the pod logs

time="2023-02-28T19:22:33Z" level=info msg="Applying CRD <http://vmwaresources.migration.harvesterhci.io|vmwaresources.migration.harvesterhci.io>"
time="2023-02-28T19:22:33Z" level=info msg="Applying CRD <http://openstacksources.migration.harvesterhci.io|openstacksources.migration.harvesterhci.io>"
time="2023-02-28T19:22:34Z" level=info msg="Applying CRD <http://virtualmachineimports.migration.harvesterhci.io|virtualmachineimports.migration.harvesterhci.io>"
time="2023-02-28T19:22:35Z" level=info msg="Starting <http://migration.harvesterhci.io/v1beta1|migration.harvesterhci.io/v1beta1>, Kind=VmwareSource controller"
time="2023-02-28T19:22:35Z" level=info msg="Starting <http://migration.harvesterhci.io/v1beta1|migration.harvesterhci.io/v1beta1>, Kind=OpenstackSource controller"
time="2023-02-28T19:22:35Z" level=info msg="reoncilling vmware migration default/vcsim"
time="2023-02-28T19:22:35Z" level=info msg="Starting <http://migration.harvesterhci.io/v1beta1|migration.harvesterhci.io/v1beta1>, Kind=VirtualMachineImport controller"
time="2023-02-28T19:22:35Z" level=info msg="Starting <http://harvesterhci.io/v1beta1|harvesterhci.io/v1beta1>, Kind=VirtualMachineImage controller"
....... [A bunch of reconciling messages, too long for slack]
time="2023-03-04T23:22:35Z" level=info msg="reoncilling vmware migration default/vcsim"
time="2023-03-05T09:22:35Z" level=info msg="reoncilling vmware migration default/vcsim"
time="2023-03-05T19:22:35Z" level=info msg="reoncilling vmware migration default/vcsim"
time="2023-03-06T05:22:35Z" level=info msg="reoncilling vmware migration default/vcsim"

salmon-city-57654

03/09/2023, 7:53 AM

hi, @rapid-flag-87720, from your comment

I tried govc as well and got the following error:

govc: Post "<https://100.80.243.158/sdk>": x509: cannot validate certificate for 100.80.243.158 because it doesn't contain any IP SANs

IIUC, we are using the govc to verify source vsphere, so it may be the root cause you see the clusterNotReady. Cc @great-bear-19718, would you have any suggestions for this?

great-bear-19718

03/14/2023, 11:59 PM

the default behaviour is to ignore ssl errors but i will check the code

7 Views

#harvester Join Slack