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 #12946] Service Groups doesn't appear in Icinga2 #501

Closed
icinga-migration opened this issue Oct 19, 2016 · 2 comments
Closed

Comments

@icinga-migration
Copy link

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

Created by swizzly on 2016-10-19 12:54:59 +00:00

Assignee: (none)
Status: Closed (closed on 2016-12-13 10:33:47 +00:00)
Target Version: (none)
Last Update: 2016-12-13 10:33:47 +00:00 (in Redmine)


Hi,

I created service groups, and then I assigned them to some of my service templates (through "main properties" / "group"), but they don't show up in icinga2. Can I assign service groups to service templates, the Director GUI allows me to do so. Then why don't they appear in icinga2?

Cheers,
Zoltan

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-12-06 08:54:59 +00:00

  • Status changed from New to Feedback
  • Assigned to set to swizzly

There used to be a related bug in Icinga 2 and I'm not sure right now whether that one has been fixed before or after the latest stable. Could you please check whether that service group has been written to a config file by Director and/or whether you see that group through the Icinga 2 API? You can use the "inspect" feature for this.

The bug I'm referring to would have caused the group to exist but to not find it's way to the IDO database.

Thanks,
Thomas

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-12-13 10:33:47 +00:00

  • Status changed from Feedback to Closed
  • Assigned to deleted swizzly

In case this is still the case please have a look at the config files generated by the Director. In case they exist and are deployed to the correct zone (default: director-global) than I could be right with my assumption. In that case please test it again with Icinga 2.6 (should be released today) and please file a new bug to the Icinga 2 project in case the problem persists.

Thanks,
Thomas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant