New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #11374] Icinga2 API: deleting service with cascade=1 does not delete dependant notification #4029
Comments
Updated by mfriedrich on 2016-03-14 12:49:41 +00:00
|
Updated by mfriedrich on 2016-03-18 10:15:55 +00:00
|
Updated by mfriedrich on 2016-05-09 11:46:15 +00:00
|
Updated by mfriedrich on 2016-05-09 11:46:28 +00:00
|
Updated by gbeutner on 2016-05-09 12:31:11 +00:00
|
Updated by gbeutner on 2016-05-09 12:31:20 +00:00
|
Updated by gbeutner on 2016-05-09 12:32:38 +00:00
Applied in changeset b8e911b. |
Updated by mfriedrich on 2016-05-11 07:39:07 +00:00
|
Updated by madsfudb on 2016-05-20 09:23:27 +00:00 Thanks for fixing! Verified with latest version 2.4.10. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11374
Created by madsfudb on 2016-03-14 12:04:28 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2016-05-09 12:32:38 +00:00)
Target Version: 2.4.8
Last Update: 2016-05-20 09:23:27 +00:00 (in Redmine)
Pre-requisites:
Steps to reproduce, all steps are completed using the API
If the host is deleted with parameter cascade=1, then both service and notification is deleted.
Attachments
Changesets
2016-05-09 12:30:12 +00:00 by gbeutner b8e911b
2016-05-12 09:08:21 +00:00 by gbeutner d82db2a
Relations:
The text was updated successfully, but these errors were encountered: