Details
-
Type:
Problem report
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: 3.0.28, 4.0.13, 4.4.0
-
Fix Version/s: 4.0.17rc1, 4.4.5rc1, 5.0.0alpha1, 5.0 (plan)
-
Component/s: Frontend (F), Server (S)
-
Team:Team C
-
Sprint:Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020)
-
Story Points:1
Description
If during trigger prototype removal process, new triggers will be discovered, it is possible to have the following error:
It may happens on big installation, if some queries are not "very very fast", but theoretically on any installation.
According PHP source code:
1. Zabbix retrieves all discovered triggers from trigger prototypes
2. Trying to remove linkage between discovered triggers and prototypes in trigger_discovery by triggerid column
3. Removes quite a lot of additional information like action conditions, services and etc (linked to triggers to be removed)
4. Removes discovered triggers
5. Removes trigger prototype
So if after 1 step new trigger will be discovered, it will be not removed at 2 step, but during 5th step foreign key constraint will be corrupted.
Probably the same issue can happen for any other resources which may be discovered automatically!