[ZBX-5968] LLD: obsoleted triggers with SNMP value in the name are not deleted when SNMP value changes Created: 2012 Dec 10  Updated: 2017 May 30  Resolved: 2013 Jan 25

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S), Templates (T)
Affects Version/s: 2.0.4
Fix Version/s: 2.0.5rc1, 2.1.0

Type: Incident report Priority: Major
Reporter: Kodai Terashima Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: lld
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1-before-host.png     PNG File 2-before-items.png     PNG File 3-before-triggers.png     PNG File 4-before-graphs.png     PNG File 5-after-host.png     PNG File 6-after-items.png     PNG File 7-after-triggers.png     PNG File 8-after-graphs.png     XML File Template_test_discovery.xml    
Issue Links:
Duplicate
is duplicated by ZBX-6071 Triggers are not deleted after LLD re... Closed

 Description   

Templated LLD doesn't delete triggers and graphs when ifAlias is changed

snmpwalk -v2c -c public localhost 1.3.6.1.2.1.31.1.1.1.18

IF-MIB::ifAlias.1 = STRING: lo
IF-MIB::ifAlias.2 = STRING: eth0

1. import attached template
2. create new host and link the template
3. LLD discover index from ifAlias and create items, triggers, graphs (screenshot 1, 2, 3, 4)
4. change ifAlias

snmpset -v2c -c public localhost 1.3.6.1.2.1.31.1.1.1.18.1 s "loopback"
snmpset -v2c -c public localhost 1.3.6.1.2.1.31.1.1.1.18.2 s "ethernet0"

5. LLD delete items immediately despite Keep lost resources period is 1 day, and doesn't delete triggers and graphs. Triggers and graphs are duplicated (screenshot 5, 6, 7, 8)

 Comments   
Comment by Fabricio Godoy [ 2013 Jan 23 ]

Is there any temporary workaround that?

Comment by Alexander Vladishev [ 2013 Jan 25 ]

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

Comment by Fabricio Godoy [ 2013 Jan 25 ]

Will be released to 2.0.5?

Comment by richlv [ 2013 Jan 25 ]

if testing and integration will be easy and quick enough, this fix might be included in 2.0.5

Comment by Oleksii Zagorskyi [ 2013 Jan 25 ]

Fabricio, it should, but need to wait to be sure.

Comment by Fabricio Godoy [ 2013 Jan 25 ]

OK, thanks.

Comment by dimir [ 2013 Jan 31 ]

Successfully tested. Please review my changes in r33302.

sasha Thanks! CLOSED

Comment by dimir [ 2013 Jan 31 ]

Fix summary.

Comment by Alexander Vladishev [ 2013 Feb 01 ]

Fixed in versions pre-2.0.5 r33317 and pre-2.1.0 (trunk) r33318.

Comment by Fabricio Godoy [ 2013 Feb 20 ]

I upgraded to 2.0.5 but orphaned triggers from 2.0.4 still lives.
How do I kill them?

Comment by richlv [ 2013 Mar 04 ]

i just tested this - created orphaned triggers with 2.0.4, upgraded to 2.0.5 and the wrong triggers disappeared.
are you sure you waited for discovery to happen again ?

Comment by Fabricio Godoy [ 2013 Mar 04 ]

Yes, but now the triggers disappeared. Took a lot of time.
3600s interval is too small?

Comment by richlv [ 2013 Mar 04 ]

they should have been removed next time discovery was run, so in your case it would have been up to one hour. so the problem is fixed

Comment by Fabricio Godoy [ 2013 Mar 04 ]

Well, I'll consider as fixed but took more than 24 hours to remove those triggers.

Generated at Sat Jun 21 08:40:33 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.