[ZBXNEXT-5850] VMware: provide Visible Name and Host Name of existing duplicate host in text of error message Created: 2020 Feb 26  Updated: 2024 Apr 10  Resolved: 2022 Jun 02

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Proxy (P), Server (S)
Affects Version/s: 4.0.18, 4.4.6, 5.0.0alpha2
Fix Version/s: None

Type: New Feature Request Priority: Major
Reporter: Edgar Akhmetshin Assignee: Michael Veksler
Resolution: Fixed Votes: 4
Labels: vmware
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
Sub-task
part of ZBXNEXT-2302 Monitoring vmware tools status Closed
part of ZBXNEXT-5778 VMware: add ability to recognise/merg... Closed
Team: Team B

 Description   

VMware host discovery uses as Host Name the UUID identifier. If we have replicated VMs between separate vCenters, but still monitored in one Zabbix, then this duplicity can occurs. (Invalid resolution of ZBX-7728 as Cannot Reproduce).

Steps to reproduce:
Two datacenters with replicated VMs for production switch. Therefore VMs are exactly same after each periodical replication. Replicated VMs are always ready to work with power on but only de-touched from network till switch process.
Now that UUID duplicity in LLD are suppressed with filters, but for regexp filters we need list of Visual hostnames, if something changed.

Result:

Cannot create host: host with the same name "5010bfff-b5fd-eeaa-8855-c0b090f60dee" already exists.

Expected:
Error message like this: Cannot create host: host with the same name "5010bfff-b5fd-eeaa-8855-c0b090f60dee" already exists [MYHOST1].



 Comments   
Comment by andres.moya [ 2020 Mar 12 ]

seems same issue after migration. I wrote template for OpenVZ and use VEID as a host name...

Comment by Michael Veksler [ 2022 Jun 02 ]

Implemented as part of ZBXNEXT-2302.
Available in:

Documentation updated:

Generated at Fri Mar 14 17:15:18 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.