Skip to content
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

Closed
icinga-migration opened this issue Mar 14, 2016 · 9 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented Mar 14, 2016

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)

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

Pre-requisites:

  • install icinga2
  • enable and setup icinga2 api feature

Steps to reproduce, all steps are completed using the API

  1. Create Host
  2. Create Service for that host
  3. Create Notification for that service
  4. Delete service with parameter "cascade=1"
  5. List all notifications, and see that notification for service still exists

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

Make sure the dependency graph is properly updated when adding and removing objects

fixes #11686
fixes #11374

2016-05-12 09:08:21 +00:00 by gbeutner d82db2a

Make sure the dependency graph is properly updated when adding and removing objects

fixes #11686
fixes #11374

Relations:

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Mar 14, 2016

Updated by mfriedrich on 2016-03-14 12:49:41 +00:00

  • Relates set to 11370
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Mar 18, 2016

Updated by mfriedrich on 2016-03-18 10:15:55 +00:00

  • Status changed from New to Assigned
  • Assigned to set to jflach
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 9, 2016

Updated by mfriedrich on 2016-05-09 11:46:15 +00:00

  • Relates deleted 11370
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 9, 2016

Updated by mfriedrich on 2016-05-09 11:46:28 +00:00

  • Parent Id set to 11415
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 9, 2016

Updated by gbeutner on 2016-05-09 12:31:11 +00:00

  • Relates set to 11686
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 9, 2016

Updated by gbeutner on 2016-05-09 12:31:20 +00:00

  • Assigned to changed from jflach to gbeutner
  • Target Version set to 2.4.8
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 9, 2016

Updated by gbeutner on 2016-05-09 12:32:38 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset b8e911b.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 11, 2016

Updated by mfriedrich on 2016-05-11 07:39:07 +00:00

  • Parent Id deleted 11415
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 20, 2016

Updated by madsfudb on 2016-05-20 09:23:27 +00:00

Thanks for fixing! Verified with latest version 2.4.10.

@icinga-migration icinga-migration added this to the 2.4.8 milestone Jan 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.