add-machine with vsphere triggers machine-0: panic: juju home hasn't been initialized

[John George]

With juju version 1.25.0-trusty-amd64 and the vsphere provider the following two commands will trigger a panic, which can be seen in the attached logs.
    JUJU_DEV_FEATURE_FLAGS="vsphere-provider" juju bootstrap --debug
    juju add-machine

environments.yaml has the following entry:
environments:
    vsphere:
        type: vsphere
        host: '192.168.1.12'
        user: '<email address hidden>'
        password: <password>
        datacenter: 'NUC-DC'
        default-series: trusty
        image-metadata-url: http://192.168.1.104
        authorized-keys: <public key>

[Sergey Matyukevich (s-matyukevich)]

Fixed in https://github.com/juju/juju/pull/3703

[Cheryl Jennings (cherylj)]

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

[John George (jog)]

This bug is fixed in 1.25.1 but not 1.26-alpha2.
Set the status for juju-core back to triaged.

[Cheryl Jennings (cherylj)]

The PR is still open and just needs to be merged. Unfortunately, master is now blocked.