[ZBX-9126] Changing prototype trigger key (expression) leaves an old version of the discovered trigger on the hosts Created: 2014 Dec 09  Updated: 2017 Aug 02  Resolved: 2014 Dec 15

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F), Server (S)
Affects Version/s: 2.4.2
Fix Version/s: 2.0.15rc1, 2.2.9rc1, 2.4.4rc1, 2.5.0

Type: Incident report Priority: Critical
Reporter: Strahinja Kustudic Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: lld, regression
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

If you change the prototype trigger key (expression), on next discovery Zabbix will leave an old trigger with the same key (expression) and create a new one besides it.

To reproduce this bug:

  1. create a prototype trigger which uses one key as a trigger expression
  2. wait for the discovery to execute to create this trigger on a host
  3. once the trigger is created, edit the prototype trigger and choose a different key in the trigger expression, but leave everything else the same
  4. wait for the discovery to execute again and you will see that the host now has two triggers with the same name, but with different trigger expressions.

I haven't tried if this happens only of I change the trigger function and not the key.



 Comments   
Comment by Alexander Vladishev [ 2014 Dec 11 ]

Similar issue with graph prototypes - second discovery fails with error:

Cannot create graph: graph with the same name "..." already exists.

Comment by Alexander Vladishev [ 2014 Dec 11 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-9126

Comment by Alexander Vladishev [ 2014 Dec 15 ]

Fixed in pre-2.0.15 r51181, pre-2.2.9 r51182, pre-2.4.4 r51183 and pre-2.5.0 (trunk) r51184.

Comment by guozhenbang [ 2017 Jul 31 ]

what's the meaning of "Fixed in pre-2.0.15 r51181, pre-2.2.9 r51182, pre-2.4.4 r51183 and pre-2.5.0 (trunk) r51184." I don't know what to do.

Comment by Rostislav Palivoda [ 2017 Aug 02 ]

Update to one of the versions (or later) where it was fixed.

Generated at Fri Mar 29 03:44:07 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.