As seen in
http://reports.vapour.ws/releases/issue/581a5bdc749a56664985fcda
There are multiple ways that a bootstrap failure can happen. I've seen that regardless of the error (stream error or failure to connect to vcenter), failure to bootstrap with vsphere as a provider always logs "failed to bootstrap model: cannot start bootstrap instance: vm '*' not found". In those cases, there's no VM or it cannot get to it while trying to clean up post error. The message is a rather catch all message which is pointing to an after the fact event.
14:15:37 DEBUG juju.service discovery.go:63 discovered init system "systemd" from series "xenial"
14:15:37 DEBUG juju.provider.vmware environ_broker.go:93 Vmware user data; 2412 bytes
14:15:38 INFO juju.provider.common destroy.go:20 destroying model "controller"
14:15:38 INFO juju.provider.common destroy.go:31 destroying instances
14:15:40 ERROR juju.cmd.juju.commands bootstrap.go:1021 error cleaning up: destroying instances: vm '*' not found
14:15:40 ERROR cmd supercommand.go:458 failed to bootstrap model: cannot start bootstrap instance: vm '*' not found
14:15:40 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:556: failed to bootstrap model} {github.com/juju/juju/provider/common/bootstrap.go:47: } {github.com/juju/juju/provider/common/bootstrap.go:178: cannot start bootstrap instance} {github.com/juju/juju/provider/vsphere/environ_broker.go:44: } {github.com/juju/juju/provider/vsphere/environ_broker.go:121: } {github.com/juju/juju/provider/vsphere/environ_availzones.go:116: } {github.com/juju/juju/provider/vsphere/environ_broker.go:162: } {github.com/juju/juju/provider/vsphere/environ_instance.go:66: } {github.com/juju/juju/provider/vsphere/client.go:214: } {vm '*' not found}])
Yes, it looks like we are not catering for situations where virtual machine finder does not find any virtual machines. Hence, the error from provider/