You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing open-vm-tools on a guest os, it is expected that all the guest properties will be populated in vm object on VCenter.
Specifically, properties under guest.net which is of type GuestNicInfo[].
However, for linux vms, the IPAddress origin property always remains unset and this leads to no information regarding if guest is using dhcp or static ip address.
For windows VMs with vmware tools installed, this property gets populated correctly.
Reproduction steps
Install open-vm-tools on VSphere VM with any linux distribution.
Expected property is not populated.
Expected behavior
IP address origin should be populated for linux VMs.
Additional context
Same behaviour of empty or unset property is observed from PowerCLI and APIs.
The text was updated successfully, but these errors were encountered:
I filed an enhancement PR to collect the optional 'origin' and 'state' fields if available from the Linux guest.
These two fields are optional information as pointed out by @pengzhencao; there is no expectations the information needs to be consistent across guest OSes.
No guarantee when or if it is possible to implement.
Describe the bug
After installing open-vm-tools on a guest os, it is expected that all the guest properties will be populated in vm object on VCenter.
Specifically, properties under
guest.net
which is of typeGuestNicInfo[]
.However, for linux vms, the IPAddress origin property always remains unset and this leads to no information regarding if guest is using dhcp or static ip address.
For windows VMs with vmware tools installed, this property gets populated correctly.
Reproduction steps
Expected behavior
IP address origin should be populated for linux VMs.
Additional context
Same behaviour of empty or unset property is observed from PowerCLI and APIs.
The text was updated successfully, but these errors were encountered: