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 #9262] cluster check w/ immediate parent and child zone endpoints #3010
Comments
Updated by mfriedrich on 2015-05-18 13:31:29 +00:00
|
Updated by mfriedrich on 2015-06-18 09:15:28 +00:00
|
Updated by mfriedrich on 2015-06-23 13:26:19 +00:00
|
Updated by mfriedrich on 2015-07-30 09:58:12 +00:00
|
Updated by mfriedrich on 2015-07-31 14:10:13 +00:00
|
Updated by mfriedrich on 2015-08-03 14:17:14 +00:00
|
Updated by Anonymous on 2015-08-03 14:17:36 +00:00
Applied in changeset d7e8d8a. |
Updated by gbeutner on 2015-08-12 08:52:13 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9262
Created by formorer on 2015-05-13 07:04:38 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-08-03 14:17:35 +00:00)
Target Version: 2.3.9
Last Update: 2015-08-12 08:52:13 +00:00 (in Redmine)
in my current setup I have master -> slave -> remote execution client, I use configuration sync to define the my configuration top-down from the master
down to my client(s). That works pretty well, to be able to resolve all objects I have to define the remote execution clients as endpoint and zone on my master, which also works.
Unfortunately the clustercheck turns red afterwards, after looking into the code it seems that the check expects all defined endpoints to be connected:
it should honor the parent setting in the object to only check its childs for connection.
Changesets
2015-07-31 14:19:58 +00:00 by (unknown) 869ab4b
2015-08-03 14:16:46 +00:00 by (unknown) d7e8d8a
2015-08-12 08:51:37 +00:00 by (unknown) b6b6115
Relations:
The text was updated successfully, but these errors were encountered: