Bootstrap with the vSphere provider fails to log into the virtual machine

[John George]

Bootstrap fails while testing the vSphere provider with juju 1.24.7 against ESXi and the VMware vCenter Server Appliance version 6.0.

environments.yaml has the following entries:
    vsphere:
        type: vsphere
        host: '192.168.1.12'
        user: '<email address hidden>'
        password: <password>
        datacenter: 'NUC-DC'
        authorized-keys: <public key>

With the following bootstrap command a virtual machine is created and started but the Juju client is not able to ssh into the newly created machine and fails (please see the attached console output).
    JUJU_DEV_FEATURE_FLAGS="vsphere-provider" juju bootstrap --debug --constraints "cpu-power=0 cpu-cores=0"

Since the virtual machine remains running after the failure (https://bugs.launchpad.net/juju-core/+bug/1510675), it's easy to examine the cloud-init configuration files:

# ls -lrth /var/lib/cloud/instance/
total 40K
drwxr-xr-x 2 root root 4.0K Oct 28 04:56 scripts
drwxr-xr-x 2 root root 4.0K Oct 28 04:56 handlers
-rw-r--r-- 1 root root 40 Oct 28 04:56 datasource
-r-------- 1 root root 6.7K Oct 28 04:56 obj.pkl
-rw------- 1 root root 0 Oct 28 04:56 user-data.txt
-rw------- 1 root root 4 Oct 28 04:56 vendor-data.txt
-rw------- 1 root root 345 Oct 28 04:56 user-data.txt.i
-rw------- 1 root root 345 Oct 28 04:56 vendor-data.txt.i
-rw------- 1 root root 0 Oct 28 04:56 cloud-config.txt
drwxr-xr-x 2 root root 4.0K Oct 28 04:56 sem
-rw-r--r-- 1 root root 51 Oct 28 04:56 boot-finished

It seems wrong that cloud-config.txt and user-data.txt are empty?

[John George (jog)]

ovf-env.xml from _ovfenv-juju-6d71e9d5-606d-44ef-8990-105da12ae3ef-machine-0.iso

[John George (jog)]

vmware.log from the ESXi host at /vmfs/volumes/562eb898-5d4fb44c-0064-b8aeed7939fd/juju-6d71e9d5-606d-44ef-8990-105da12ae3ef-machine-0/

[John George (jog)]

juju-6d71e9d5-606d-44ef-8990-105da12ae3ef-machine-0.vmx from the ESXi host at /vmfs/volumes/562eb898-5d4fb44c-0064-b8aeed7939fd/juju-6d71e9d5-606d-44ef-8990-105da12ae3ef-machine-0/

[John George (jog)]

trusty-server-cloudimg-amd64.ovf from the ESXi host at /vmfs/volumes/562eb898-5d4fb44c-0064-b8aeed7939fd/juju-6d71e9d5-606d-44ef-8990-105da12ae3ef-machine-0/

[Katherine Cox-Buday (cox-katherine-e)]

This bug has the same root cause as bug 1468383.

[John George (jog)]

To work around this issue, I hosted a local image streams directory (e.g. cd vsphere; sudo python -m SimpleHTTPServer 80)
The directory structure is:
vsphere/
vsphere/server
vsphere/server/releases
vsphere/server/releases/trusty
vsphere/server/releases/trusty/release-20151103
vsphere/server/releases/trusty/release-20151103/test.ova
vsphere/streams
vsphere/streams/v1
vsphere/streams/v1/index.json
vsphere/streams/v1/com.ubuntu.cloud:released:download.json

test.ova was downloaded from the link in https://bugs.launchpad.net/cpc-core/+bug/1468383/comments/10
I'll attach index.json and com.ubuntu.cloud:released:download.json

Then add the following line to environment.yaml for the vsphere environment:
image-metadata-url: http://<IP or hostname of the http server>

[Sergey Matyukevich (s-matyukevich)]

This happened because of wrong OVA images. This bag have the same root case https://bugs.launchpad.net/cpc-core/+bug/1468383 This bug should be fixed, if you use correct ova image.

[Cheryl Jennings (cherylj)]

1.25 fix: https://github.com/juju/juju/pull/3729