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 #11065] Deleting an object via API does not disable it in DB IDO #3889
Comments
Updated by mfriedrich on 2016-02-04 15:22:29 +00:00
|
Updated by mfriedrich on 2016-02-04 16:13:13 +00:00
|
Updated by mfriedrich on 2016-02-05 11:36:29 +00:00 Found it. When ensuring to remove duplicated config updates we changed the DeactivateObject condition. When an object gets deleted we need to ensure that it is deactivated inside the database. It may happen that for some reason the dbActive flag is already set to false (was not enabled before) which will then cause the condition to fail and the object remains active.
|
Updated by mfriedrich on 2016-02-05 11:37:58 +00:00
Applied in changeset 4049cc0. |
Updated by gbeutner on 2016-02-23 09:58:45 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11065
Created by mfriedrich on 2016-02-01 17:47:25 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-02-05 11:37:58 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:45 +00:00 (in Redmine)
Changesets
2016-02-05 11:37:00 +00:00 by mfriedrich 4049cc0
2016-02-23 08:43:41 +00:00 by mfriedrich 7cbe1c4
Relations:
The text was updated successfully, but these errors were encountered: