[ZBX-13611] Successfull LLD rule processing does not update configuration cache Created: 2018 Mar 13  Updated: 2024 Apr 10  Resolved: 2018 Mar 25

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.4.7
Fix Version/s: 3.4.8rc1, 4.0.0alpha5, 4.0 (plan)

Type: Problem report Priority: Trivial
Reporter: Andris Zeila Assignee: Andris Zeila
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team A
Sprint: Sprint 30
Story Points: 0.5

 Description   

When LLD rule check fails with not supported error it is put into history cache and processed by history syncers. The item state and error is compared with configuration cache state/error and cache/database is updated only if values differ.

When LLD rule check succeeds it updates its state/error in database, but in configuration cache the old state/error remains.

While it doesn't seem correct to have the supported/notsupported rule processing split, for now it would be easier to simply update configuration cache when resetting item state/error after successfull lld check.

 Comments   
Comment by Andris Zeila [ 2018 Mar 19 ]

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

Comment by Vladislavs Sokurenko [ 2018 Mar 20 ]

Steps to reproduce original issue:
1. Create discovery rule for file contents vfs.file.contents.
2. Make sure it becomes unsupported due to file missing. (it has now become unsupported in configuration cache)
3. Now make discovery rule become supported by creating file. (configuration cache is not updated)
4. See that everything is successfully discovered.
5. Delete file once again.

Expected:
Discovery item is unsupported once again.

Actual:
It is still supported however nothing is discovered.

Comment by Vladislavs Sokurenko [ 2018 Mar 20 ]

Successfully tested.

Comment by Andris Zeila [ 2018 Mar 22 ]

Released in:

  • pre-3.4.8rc1 r78900
  • pre-4.0.0alpha5 r78901
Comment by Maksims Edelmans [ 2018 Oct 11 ]

Hello Team,

Is it fixed in 3.4.14?

It seems that I have exactly the same problem in 3.4.14.

I have a LLD rule (snmp discovery) that is in 'Not supported' state:

"Invalid SNMP OID: pairs of macro and OID are expected."

I have fixed this by changing incorrect entry with " discovery{#SNMPVALUE},.1.3.6.1.2.1.15.3.1.7 "

But status doesn't update (5m update interval).

Generated at Wed Apr 24 04:52:20 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.