[ZBX-21162] Issue with monitoring multiple kubernetes/openshift clusters Created: 2022 Jun 03 Updated: 2022 Sep 27 Resolved: 2022 Sep 27 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Templates (T) |
Affects Version/s: | 6.0.5 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Rudolf Kastl | Assignee: | Elina Kuzyutkina (Inactive) |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
RHEL 8 |
Issue Links: |
|
Description |
Steps to reproduce:
Result: Detected nodes are only getting added to the correct host groups with the first cluster monitored. Expected:
Workaround: The only alternative currently is to create copies of the templates for each individual cluster and adjust the groupnames in the copies of the templates. |
Comments |
Comment by Alexey Pustovalov [ 2022 Jun 03 ] |
Dear Rudolf, Could you show us exact error message you seen? |
Comment by Rudolf Kastl [ 2022 Jun 03 ] |
Cannot create group: group with the same name "Kubernetes/Nodes/Role: master" already exists. Cannot create group: group with the same name "Kubernetes/Nodes/Role: worker" already exists. ^^ this is taken from a "red exclamation mark" next to: Node LLD: Cluster node discovery The host prototype for this rule actually has a group prototype "Kubernetes/Nodes/Role: {#ROLES}". |
Comment by Elina Kuzyutkina (Inactive) [ 2022 Jun 03 ] |
Hi, Regards, Elina |
Comment by Rudolf Kastl [ 2022 Jun 03 ] |
Elina, I like your idea of adding the Cluster Name into the group Name because that makes handling of a larger amount of clusters more easy and it looks more tidy. But this is not working since that variable is not allowed to be used with group prototypes. If i try to save that change i get:
|
Comment by Elina Kuzyutkina (Inactive) [ 2022 Jun 03 ] |
Please give me some time I'll try to reproduce this |
Comment by Elina Kuzyutkina (Inactive) [ 2022 Jun 03 ] |
Can you check which host group has id 130? (you can simply find it in the address bar when Host group configuration window is open) |
Comment by Rudolf Kastl [ 2022 Jun 03 ] |
https://...hostgroups.php?form=update&groupid=130 No permissions to referred object or it does not exist! |
Comment by Elina Kuzyutkina (Inactive) [ 2022 Jun 06 ] |
Hi, I can't reproduce the error with the group. You can now describe the sequence of your actions - this will simplify the task |
Comment by Elina Kuzyutkina (Inactive) [ 2022 Jun 06 ] |
{HOST.HOST} or {HOST.NAME} really won't work here. I have created By error of deleting a group, I can’t reproduce it in any way - I at least need that order of actions you have done (adding hosts, linking-unlinking a template, deleting-adding groups, etc). |
Comment by Rudolf Kastl [ 2022 Jun 07 ] |
The "deletion" is not really a "deletion" in the sense of trying to delete a group. It just happens if i add the {HOST.NAME} to the group prototype and try to save it. Thanks for opening the new bug! Thank you for looking into the problem! |
Comment by Elina Kuzyutkina (Inactive) [ 2022 Jun 08 ] |
Hi, |
Comment by Rudolf Kastl [ 2022 Jun 13 ] |
Hi Elina, Sorry for the late reply, actually i had time to toy a bit with changing the group prototype with the host prototype. For some reason i can not change to anything else even adding some simple "test" string to the actual group name does not work. I was able to change it some point, before i had added the template to the hosts and it discovered nodes. Hope this helps. |