The VM 'ip address' being returned from the vSphere API (via rbvmomi) is incorrect in cases where Docker (or presumably other packages/user provisioning) assigns a 'virtual' bridge interface and/or other container interfaces.
For example, for a VM with the following interfaces:
Vsphere assumes the machine default API is '172.19.0.1' (a bridge adapter IP created by docker compose in this case), attempts to reprovision/ssh/etc the VM will fail as the bridge interface isn't accessible outside the VM.
Inspecting the values coming back up from the api (through rbvmomi):
The VM 'ip address' being returned from the vSphere API (via rbvmomi) is incorrect in cases where Docker (or presumably other packages/user provisioning) assigns a 'virtual' bridge interface and/or other container interfaces.
For example, for a VM with the following interfaces:
Vsphere assumes the machine default API is '172.19.0.1' (a bridge adapter IP created by docker compose in this case), attempts to reprovision/ssh/etc the VM will fail as the bridge interface isn't accessible outside the VM.
Inspecting the values coming back up from the api (through rbvmomi):
Given I believe this is a vsphere api issue, we should (optionally) handle this in the plugin.