We are noticing an oddity in the frontend in 2.2.4 and 2.2.5, though it’s not present in 2.2.3. We’ve tested pretty extensively. I’ve looked through this forum as well as the Zabbix JIRA and not found a report of a similar issue.
Wondering if we’ve got a bug or if I’ve missed the report of it somewhere…hence this post.
Our environment overview:
Zabbix 2.2.3 on CentOS 6.4; 3-node cluster
Server/JGate/Frontend running on isolated host (Linux HA using Corosync/Pacemaker)
Frontend being served by optimized NGINX using php-fpm
Data layer running on isolated host (Percona XtraDB Cluster - built-in Galeara)
Overview of oddity:
For purposes of explanation, assume we have…
1 user group — User_Group_1
26 host groups - Host_Group_A .. Host_Group_Z
Description of oddity:
When setting Permissions for User_Group_1, perform the following:
1. Navigate the frontend to the Permissions tab under User_Group_1
2. Under “Read-write” or “Read only”, click “Add”
3. Select Host_Group_A, Host_Group_B, Host_Group_C, and click “Select”
Result is, under the “Composing permissions” boxes at top of page, Host_Group_A, Host_Group_B, Host_Group_C are properly displayed in the “Read-write” or “Read only” boxes as applicable. However…under the “Calculated permissions” boxes at middle and bottom of page, Host_Group_J, Host_Group_X, Host_Group_M and their associated hosts are displayed.
Upon clicking “Save” and then re-examining the Permissions for User_Group_1, the permissions for Host_Group_J, Host_Group_X, Host_Group_M remain present…which is undesirable, but at least consistent with permissions calculation from previous screen.
Other observations (still using example values from above):
1. The incorrect permissions calculations are not random. Example: when selecting Host_Group_A, you will get Host_Group_J incorrectly calculated every time.
2. Some of the host groups will calculate correctly, but these appear to be very few in number (we’ve only noticed a couple that do this) and the host groups in question can still be incorrectly calculated by selecting another host group. Example: when selecting Host_Group_J, Host_Group_J is correctly calculated, but Host_Group_J is still incorrectly calculated when selecting Host_Group_A
3. There seems to be no constant offset in host group incorrect calculations. Example: when selecting Host_Group_A and Host_Group_B, one does NOT end up with Host_Group_A+10 and Host_Group_B+10.
This feels like some kind of database corruption. However, we’ve tested against both old and current copies of the database in our DEV environment, and verified behavior across all nodes in the cluster, and verified across multiple browsers, and tested against 2.2.3, 2.2.4, and 2.2.5.
Both 2.2.4 and 2.2.5 have this oddity, while switching back to 2.2.3 makes everything happy again.
Any assistance/suggestions would be greatly appreciated. Many thanks for reading.
Wondering if we’ve got a bug or if I’ve missed the report of it somewhere…hence this post.
Our environment overview:
Zabbix 2.2.3 on CentOS 6.4; 3-node cluster
Server/JGate/Frontend running on isolated host (Linux HA using Corosync/Pacemaker)
Frontend being served by optimized NGINX using php-fpm
Data layer running on isolated host (Percona XtraDB Cluster - built-in Galeara)
Overview of oddity:
For purposes of explanation, assume we have…
1 user group — User_Group_1
26 host groups - Host_Group_A .. Host_Group_Z
Description of oddity:
When setting Permissions for User_Group_1, perform the following:
1. Navigate the frontend to the Permissions tab under User_Group_1
2. Under “Read-write” or “Read only”, click “Add”
3. Select Host_Group_A, Host_Group_B, Host_Group_C, and click “Select”
Result is, under the “Composing permissions” boxes at top of page, Host_Group_A, Host_Group_B, Host_Group_C are properly displayed in the “Read-write” or “Read only” boxes as applicable. However…under the “Calculated permissions” boxes at middle and bottom of page, Host_Group_J, Host_Group_X, Host_Group_M and their associated hosts are displayed.
Upon clicking “Save” and then re-examining the Permissions for User_Group_1, the permissions for Host_Group_J, Host_Group_X, Host_Group_M remain present…which is undesirable, but at least consistent with permissions calculation from previous screen.
Other observations (still using example values from above):
1. The incorrect permissions calculations are not random. Example: when selecting Host_Group_A, you will get Host_Group_J incorrectly calculated every time.
2. Some of the host groups will calculate correctly, but these appear to be very few in number (we’ve only noticed a couple that do this) and the host groups in question can still be incorrectly calculated by selecting another host group. Example: when selecting Host_Group_J, Host_Group_J is correctly calculated, but Host_Group_J is still incorrectly calculated when selecting Host_Group_A
3. There seems to be no constant offset in host group incorrect calculations. Example: when selecting Host_Group_A and Host_Group_B, one does NOT end up with Host_Group_A+10 and Host_Group_B+10.
This feels like some kind of database corruption. However, we’ve tested against both old and current copies of the database in our DEV environment, and verified behavior across all nodes in the cluster, and verified across multiple browsers, and tested against 2.2.3, 2.2.4, and 2.2.5.
Both 2.2.4 and 2.2.5 have this oddity, while switching back to 2.2.3 makes everything happy again.
Any assistance/suggestions would be greatly appreciated. Many thanks for reading.
Comment