We have seen scenarios where due to the wrong FQDN\Hostname set for an ESX, virt-who grabs duplicate hostname of ESX but reports correct mapping based on UUID.
So unless someone knows how to figure out this duplication and then asks the user to check back in vCenter, we will always assume that virt-who is either missing one hypervisor to report or reporting duplicate host-guest mapping for the same hostname.
The expectation is to have a rake or PowerShell script that can log in to vCenter, check all hypervisors, and then collect the following data.
hypervisor name, hypervisor hostname set i.e. $esxcli.system.hostname.get() data, dmi:uuid set for the hypervisor
It could be too much to ask but considering the magics you can do, I thought opening an issue will be a good way to start this discussion.
We have seen scenarios where due to the wrong FQDN\Hostname set for an ESX, virt-who grabs duplicate hostname of ESX but reports correct mapping based on UUID.
So unless someone knows how to figure out this duplication and then asks the user to check back in vCenter, we will always assume that virt-who is either missing one hypervisor to report or reporting duplicate host-guest mapping for the same hostname.
The expectation is to have a rake or PowerShell script that can log in to vCenter, check all hypervisors, and then collect the following data.
hypervisor name, hypervisor hostname set i.e. $esxcli.system.hostname.get() data, dmi:uuid set for the hypervisor
It could be too much to ask but considering the magics you can do, I thought opening an issue will be a good way to start this discussion.