Another observation here is that the directory: /tmp/juju-juju-vsphere-bionic created on the client-side of juju as part of a bootstrap command will be left in place.
The consequence of that, is that other users trying to bootstrap against the same cloud-substrate will fail. We hit that problem and it was non trivial to fix and would also require root-privilege to remove the directory or change permissions.
Suggestion: Remove the /tmp/juju-juju-vsphere-bionic directory as part of cleaning up the bootstrap command so to prevent this from happening.
Another observation here is that the directory: /tmp/juju- juju-vsphere- bionic created on the client-side of juju as part of a bootstrap command will be left in place.
The consequence of that, is that other users trying to bootstrap against the same cloud-substrate will fail. We hit that problem and it was non trivial to fix and would also require root-privilege to remove the directory or change permissions.
Suggestion: Remove the /tmp/juju- juju-vsphere- bionic directory as part of cleaning up the bootstrap command so to prevent this from happening.