[dev.icinga.com #13939] acknowledge-problem api sending notifications when notify is false

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/13939

Created by djalden on 2017-01-10 20:28:21 +00:00

Assignee: mfriedrich
Status: Assigned
Target Version: (none)
Last Update: 2017-01-12 10:46:57 +00:00 (in Redmine)

Icinga Version: 2.6.0
Backport?: Not yet backported
Include in Changelog: 1

---

Hi,
I've setup icingaweb2 on a separate server and have run into what I believe is a bug. If I ack an issue with icingaweb and deselect "Send Notification", a notification still goes out. I've looked at the debuglog on the icingaweb2 server and it shows:

...,notify.

so I believe it's doing it right - but I still get a notification. If I do the same thing with the icingaweb2 on the same server (so it's using the command pipe instead of the API), I do not get a notification.
...dave

Attachments

• icingaweb-debug.log djalden - 2017-01-11 17:37:30 +00:00
• icinga-debug.log djalden - 2017-01-11 17:37:37 +00:00

Changesets

2017-01-12 10:43:22 +00:00 by mfriedrich 8196523

Fix notify/sticky parameter handling in 'acknowledge-problem' API action

refs #13939

[icinga-migration]

Updated by mfriedrich on 2017-01-11 16:58:01 +00:00

• Status changed from New to Feedback
• Assigned to set to djalden

Can you please extract the entire curl request and the corresponding icinga2 debug log entries for such a notification being triggered?

[icinga-migration]

Updated by djalden on 2017-01-11 17:37:40 +00:00

• File added icingaweb-debug.log
• File added icinga-debug.log

Sure - I've attached the debug information. I tried to extract the relevant parts from the icinga debug file (in the 15 seconds I turned on debug, it generated 33,686 lines of information :). Let me know if I butchered it and you need more of the debug file.

[icinga-migration]

Updated by mfriedrich on 2017-01-12 10:46:57 +00:00

• Status changed from Feedback to Assigned
• Assigned to changed from djalden to mfriedrich

Alright, I see it. Pushed a fix to a branch waiting for review and tests.