[dev.icinga.com #12606] Config validation should complain about disabled API

[icinga-migration]

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

Created by mfrosch on 2016-08-31 15:23:51 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-09-02 07:00:29 +00:00 (in Redmine)

Icinga Version: 2.5.3-80-g01b23ee
Backport?: Not yet backported
Include in Changelog: 1

---

Noticed the following in a test environment:

• Icinga 2 configured with Zone + Endpoint
• API disabled, since its currently only one Node
• Checks assigned to Zone master (zones.d)

Result:

• Config is validated without a warning
• Running, but all checks in zone master PENDING, never to be checked

Expected:

• Icinga should complain that complex zoning (more than 1 Zone or EP) needs API
• Still check the checkables(???)

[icinga-migration]

Updated by mfrosch on 2016-09-01 12:01:23 +00:00

This definitely is a problem of the Zone, when I move the data in conf.d the checkables are actually checked.

[icinga-migration]

Updated by gbeutner on 2016-09-02 07:00:29 +00:00

The problem is that without the ApiListener object Icinga doesn't know which zone it belongs to (it does this by loading the .crt file in ApiListener::OnConfigLoaded) - which means it won't un-pause those objects in ApiListener::UpdateObjectAuthority.

[dnsmichi]

I don't see a way to properly fix this, other than verifying on your own that all requirements are fulfilled.