[ZBX-20600] Failed to retrieve hv.datastore.latency item when multiple datastores with duplicate name are mounted on hv. Created: 2022 Feb 17  Updated: 2024 Apr 10  Resolved: 2022 May 24

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: 4.0.41rc1, 5.0.24rc1, 6.0.5rc1, 6.2.0beta3, 6.2 (plan)

Type: Problem report Priority: Major
Reporter: Hayato Watanabe Assignee: Michael Veksler
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 4.0.35


Issue Links:
Causes
causes ZBX-21137 Zabbix crash due vmware collector Closed
Duplicate
Sub-task
part of ZBX-23667 Please provide patch for 6.0 to use U... Closed
Team: Team B
Sprint: Sprint 87 (Apr 2022), Sprint 88 (May 2022)
Story Points: 1

 Description   

Environment:

Several hypervisors are managed by a vCenter, one datastore is mounted on each hypervisors with same datastore name.

                |-- hv1 --|
vCenter -|-- hv2 --|- datastoreA
                |-- hv3 --|

Problem:

Zabbix default vmware template discover 3 datastore on each hypervisor host, but only one hv.datastore.latency item can work, others become not supported with the error below.

Unknown hypervisor "HYPERVISOR NAME" for datastore "DATASTORE NAME"

The problem doesn't happen if datastore name are different, like:

hv1 - datastoreA-1 --|
hv2 - datastoreA-2 --|- datastoreA
hv3 - datastoreA-3 --|

There was no problem on Zabbix 2.2 with same datastore name, problem happens on 4.0.

Also, latency information in datastore.read and datastore.write of vCenter host are calculated by Zabbix server from total latency value of hypervisor, so latency item on vCenter host is incorrect, it uses only one hv.datastore.latency item value.



 Comments   
Comment by Michael Veksler [ 2022 Apr 22 ]

Dear hayato.watanabe, may I ask you to test this fix (PR#3808) ?

If needed, I can attach the new binary.

Comment by Michael Veksler [ 2022 May 12 ]

Available in:

Generated at Fri May 02 10:30:48 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.