Hi All,
I've noticed some strange behaviour. Our Zabbix 4.4.4 is:
1. Discovering VMWare Hypervisors, these are monitored correctly for a while, sometimes months
2. The discovered HV or VM is then "lost" (i.e. Zabbix is not able to discover the HV and is waiting to delete the lost resource: The host is not discovered anymore and will be deleted in 9d 21h 11m )
3. At the same time as 2 another HV has been discovered but with a different UUID but same name. The host cannot be added again because the visible name would match the visible name of the HV in 2
This feels like a bug or the UUID is not permanent on an HV for some reason.
Something similar also seems to be going on with guest VMs
What exactly is hv.uuid in vmware terms as we have been unable to find it?
Thanks
Nic
I've noticed some strange behaviour. Our Zabbix 4.4.4 is:
1. Discovering VMWare Hypervisors, these are monitored correctly for a while, sometimes months
2. The discovered HV or VM is then "lost" (i.e. Zabbix is not able to discover the HV and is waiting to delete the lost resource: The host is not discovered anymore and will be deleted in 9d 21h 11m )
3. At the same time as 2 another HV has been discovered but with a different UUID but same name. The host cannot be added again because the visible name would match the visible name of the HV in 2
This feels like a bug or the UUID is not permanent on an HV for some reason.
Something similar also seems to be going on with guest VMs
What exactly is hv.uuid in vmware terms as we have been unable to find it?
Thanks
Nic