-
Problem report
-
Resolution: Fixed
-
Major
-
6.0.1
-
None
-
SLES 15 sp3, PostgreSQL v13, Zabbix server compiled from a sources
-
Sprint 86 (Mar 2022), Sprint 87 (Apr 2022)
-
0.25
Steps to reproduce:
- Install a Zabbix Server v5.0 (LTS);
- Set up some services ("Configuration" -> "Services"), for example:
- "LDAP pseudo-cluster": has the status calculation algorithm as "Problem, if all children have problems";
- two child services: "ldap1 node" and "ldap2 node" with the status calculation algorithm as "Problem, if one child has a problem";
- Perform on-site upgrade onto Zabbix v6.0;
- After Zabbix server v6.0 is started and the database has been converted, look at the menu "Services" -> "Services" and check the appropriate services.
Result:
The calculation algorithm "Problem, if all children have problems" has been converted onto "Most critical of the [any] child services", but "Problem, if one child has a problem" – onto "Most critical if all children have problems".
It causes to the wrong parent service calculations when the child is failed.
See the screenshots attached:
- "all children" in v5.0:
- the same service after conversion in v6.0:
- "one child" in v5.0:
- the same service in v6.0:
Expected:
Just opposite conversion:
Problem, if all children have problems | -> | Most critical if all children have problems |
Problem, if one child has a problem | -> | Most critical of the child services |