[dev.icinga.com #949] Optionally allow empty hostgroup assigment for services #436
Comments
Updated by mfriedrich on 2010-11-03 15:32:02 +00:00
|
Updated by mfriedrich on 2010-11-24 09:11:17 +00:00 normal behavior
having the patch applied, the proposed example lacks of a host_name in the service definition which will lead the service into not being registered correctly. nagios ignores that while icinga spits out an error. so this needs further investigation. |
Updated by mfriedrich on 2010-12-03 15:47:38 +00:00
|
Updated by mfriedrich on 2010-12-17 16:29:25 +00:00
|
Updated by mfriedrich on 2010-12-17 19:52:56 +00:00
Applied in changeset commit:"305ec37a447bda3333de8c5574d20ecc70629532". |
Updated by mfriedrich on 2012-02-17 21:24:40 +00:00
this does not properly work, because icinga threats the first and secondary loop differently (and ofc wrong). original
modified to warn the user about some possible missing attributes:
the first condition let's things pass through, even if checking allow_empty_hostgroups_assignment before, and then being inserted to objects_skiplist either way, resulting in the final error of missing an important attribute when registering to the core. |
Updated by mfriedrich on 2012-02-23 18:41:13 +00:00
finally fixed correctly. in master and next (which will be the source for r1.7) |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/949
Created by mfriedrich on 2010-11-02 16:58:57 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2012-02-23 18:41:13 +00:00)
Target Version: 1.7
Last Update: 2012-02-23 18:41:13 +00:00 (in Redmine)
Attachments
Changesets
2010-12-17 16:44:13 +00:00 by mfriedrich 305ec37
2012-02-17 21:25:11 +00:00 by mfriedrich c440478
Relations:
The text was updated successfully, but these errors were encountered: