vmware.hv.discovery-error.png
|
Causes |
|||
|
Duplicate |
Team A
[ZBX-9011] 'Cannot create group: invalid group name "".' error on vmware.hv.discovery Created: 2014 Nov 10 Updated: 2024 Apr 10 Resolved: 2018 Dec 02 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 2.2.7, 3.0.23, 3.4.14, 4.0.1 |
| Fix Version/s: | 4.0.3rc1, 4.2.0alpha2, 4.2 (plan) |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Kodai Terashima | Assignee: | Michael Veksler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | item, lld, vmware | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ESXi 5.5, vCenter 5.5, vCenter 6.5, vCenter 6.7 |
||
| Attachments: |
vmware.hv.discovery-error.png
|
||||||||
| Issue Links: |
|
||||||||
| Team: | Team A | ||||||||
| Team: | Team A |
||||||||
| Sprint: | Sprint 46, Nov 2018 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
An error 'Cannot create group: invalid group name "".' is displayed on web frontend vmware.hv.discovery item when linking a template "Template Virt VMware". It seems that Hypervisors and VMs are discovered and registered as hosts correctly, just the error above is displayed. |
| Comments |
| Comment by Alexander Vladishev [ 2014 Nov 10 ] |
|
I think it is not a bug. Probably a lld macro used in host prototype resolves as an empty string. Please check it. |
| Comment by Kodai Terashima [ 2014 Nov 10 ] |
|
This error is from {#CLUSTER.NAME} in group prototype. Just removing it solved this issue. closed. |
| Comment by Glebs Ivanovskis (Inactive) [ 2016 Aug 22 ] |
|
It's a bug in our templates, still present in trunk. {#CLUSTER.NAME} is used as group prototype name while our documentation clearly says:
|
| Comment by Constantin Oshmyan [ 2018 Nov 08 ] |
|
Hi, we have the same problem. We have a big enough VMware infrastructure. The most of hypervisors are clustered, therefore the usage of these groups is comfortable. However, some hypervisors are standalone. They are not members of any cluster, so the {#CLUSTER.NAME} macro is resolved to empty string for them. Is it possible, nevertheless, to just ignore the group prototypes with an empty names (instead of reporting an errors)? |
| Comment by Michael Veksler [ 2018 Nov 30 ] |
|
Available in:
|