Skip to content
This repository has been archived by the owner. It is now read-only.

[dev.icinga.com #5697] service escalations with no host mapping are not accepted #1440

Closed
icinga-migration opened this issue Feb 26, 2014 · 2 comments
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Feb 26, 2014

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

Created by tombstone on 2014-02-26 14:36:16 +00:00

Assignee: (none)
Status: Resolved (closed on 2014-03-03 19:56:17 +00:00)
Target Version: 1.11
Last Update: 2014-03-03 19:56:17 +00:00 (in Redmine)

Icinga Version: icinga-1.10.3
OS Version: Scientific Linux 6.5

dummy config:

define hostgroup {
    hostgroup_name empty_hostgroup
    alias brmbrm
}
define service {
    hostgroup_name empty_hostgroup
    service_description dummy_service
}
define serviceescalation {
    hostgroup_name empty_hostgroup
    service_description dummy_service
}

Configuration above fails with

Could not expand hostgroups and/or hosts specified in service escalation. Error processing object config files!

attaching patch for possible fix, based on solution for #3961

Attachments

Changesets

2014-03-03 19:55:35 +00:00 by tombstone 0e6cdfc

Accept/ignore service escalation with no host mappings.

Fixes #5697

Signed-off-by: Michael Friedrich <Michael.Friedrich@netways.de>
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 3, 2014

Updated by mfriedrich on 2014-03-03 19:56:13 +00:00

  • Target Version set to 1.11

Thanks for the patch, applied to git next.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Mar 3, 2014

Updated by tombstone on 2014-03-03 19:56:17 +00:00

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

Applied in changeset 0e6cdfc.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.