Hot Shot
Hot Shot

VIO 7 VDS deployment does not finish

Jump to solution

I try to deploy a new VIO 7 HA, VDS deployment.

At the end the deployment wizard does not close the window if I press on the finish "button", but the deployment starts if i press cancel and refresh the window (maybe a UI issue).

The manager does not make any changes in the vCenter (like adding portgroups etc.) And the status stays at "validating"

If i login to the manager and do a "kubectl get pods -A" I get a Pod with error state:

...

openstack            create-objects-neutron-neutron1-262ksqffhf-bj89d                  0/1     Error       0          2m20s

...

but the log does not show something meaningful to me:

kubectl logs create-objects-neutron-neutron1-262ksqffhf-bj89d -n openstack

time="2020-07-14T09:38:56Z" level=info msg="successfully created k8sClientSet"

time="2020-07-14T09:38:56.18Z" level=info msg="detecting plugin configuration and parent resource" kind=Neutron name=neutron1 namespace=openstack

time="2020-07-14T09:38:56.183Z" level=error msg="failure while fetching parent resource for Neutron 'neutron1' (namespace='openstack'): vcenters.vio.vmware.com \"vcenter1\" not found" kind=Neutron name=neutron1 namespace=openstack

time="2020-07-14T09:38:56.183Z" level=fatal msg="failure while fetching parent resource for Neutron 'neutron1' (namespace='openstack'): vcenters.vio.vmware.com \"vcenter1\" not found"

Does anybody know how to debug this further?

0 Kudos
1 Solution

Accepted Solutions
Hot Shot
Hot Shot

With VMware support and engineering we could solve this issue.

Our vCenter has a ID containing uppercase letters, the installer does not like this.

VMware enginneering provides me a patch to solve this, maybe they will fix it in a future version.

View solution in original post

0 Kudos
1 Reply
Hot Shot
Hot Shot

With VMware support and engineering we could solve this issue.

Our vCenter has a ID containing uppercase letters, the installer does not like this.

VMware enginneering provides me a patch to solve this, maybe they will fix it in a future version.

View solution in original post

0 Kudos