[ZBX-13001] Manually closed recovery action - problem Created: 2017 Nov 08  Updated: 2017 Dec 07  Resolved: 2017 Dec 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.2.9
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Grzegorz Grabowski Assignee: Unassigned
Resolution: Unsupported version Votes: 0
Labels: actionoperations, recovery, zabbix_server
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos7, Mariadb

Attachments: JPEG File action.jpg     JPEG File screen.jpg    

 Description   

Bug #1

Steps to reproduce:
1. Set the action with only one item "Run remote commands on current host - Zabbix Server"
2. Set the Recovery operations to one item "Run remote commands on current host - Zabbix Server"

Close the problem manually by ACK with Action "Close"

Result:
Recovery action is not triggered at all.

Expected:
Recovery action should be triggered.

Workaround
1. Add the second item to Recovery operations "Notify all who received any messages regarding the problem before" - and then remote command will be run.

Bug#2
The same above, when workaround is applied, macros:

{EVENT.RECOVERY.DATE} {EVENT.RECOVERY.TIME} {EVENT.RECOVERY.ID}

- maybe more?
is not resolved at all.
Macro:

{EVENT.AGE}

has always 0m.
Macro

{EVENT.ID} - has some "hidden event number" but not as documented "Use the {EVENT.ID}

macro to reference the original problem" so cant to reference to original one.

{EVENT.DATE}

and more are not reference to original (start) problem.

As you can see on screenshot.

 Comments   
Comment by Vladislavs Sokurenko [ 2017 Nov 08 ]

Could you please be so kind and confirm if it works in 3.4 as expected ?

Comment by Grzegorz Grabowski [ 2017 Nov 08 ]

Action definition

Comment by Grzegorz Grabowski [ 2017 Nov 08 ]

Need an hour to confirm it.

Comment by Grzegorz Grabowski [ 2017 Nov 08 ]

Confirmed. This error does not occur on 3.4.3 at all.

Comment by Grzegorz Grabowski [ 2017 Nov 08 ]

But you consider NOT USE " - double quote - inside

{EVENT.ACK.HISTORY}

because this crush command line parameters.

Comment by Rostislav Palivoda [ 2017 Nov 08 ]

It looks like issue introduced in 3.2 version that is very close to EOL.
Would it be possible for you to switch to 3.4 release? By the way we just released packages for fresh 3.4.4 version. mbsit

Comment by Ingus Vilnis [ 2017 Dec 07 ]

Hi Grzegorz,

As stated previously the issue can not be reproduced in the latest Zabbix 3.4, but 3.2. is not supported with fixes anymore.

Please try upgrade.
Closing due to no further activity for a longer time.

Generated at Thu Apr 18 22:54:31 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.