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 #10980] icinga2 node update-config does not work well with indirect connected zones #3849
Comments
Updated by mfriedrich on 2016-01-29 09:27:20 +00:00
|
Updated by DreiIT on 2016-02-10 11:49:41 +00:00 I can confirm the problem, reported by formorer. The zones in my scenario are connected in following way: When icinga2 node update-config is run, the parents were not generated correctly:
Also the check_command of the host 'sscript01.ifs.loc' should be 'dummy'. |
Updated by DreiIT on 2016-02-10 15:00:31 +00:00 Correction: I had an error in my config, the check_command of 'sscript01.ifs.loc' is set right:
|
Updated by vishnu on 2016-02-22 13:32:07 +00:00 I face the same issue too. As formorer said, I had to change zones/client-of-client.conf to change parent to client and hosts/client-of-client.conf to change check_command to "dummy" from "cluster-zone" to make host and services of client-of-client green in master's icingaweb2. Waiting for the fix. |
Updated by mfriedrich on 2016-03-18 14:36:18 +00:00 That involves larger changes to how the configuration is pushed from clients to master (include satellites as "proxy"). This is currently not planned to be implemented soon. |
Updated by mfriedrich on 2016-03-18 14:37:50 +00:00
|
Updated by mfriedrich on 2016-11-18 17:11:13 +00:00
|
Updated by mfriedrich on 2016-11-23 14:57:26 +00:00
|
Updated by mfriedrich on 2017-01-14 13:05:56 +00:00
|
Updated by mfriedrich on 2017-01-14 13:08:03 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10980
Created by formorer on 2016-01-18 14:47:30 +00:00
Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2017-01-14 13:05:56 +00:00 (in Redmine)
Hi,
I have the following setup
master <- client <- client_of_client where "client_of_client" is connected via client to my master instance.
I do propagate configuration files from my clients to the master with icinga2 update-config.
Unfortunately the generated configuration files for the client_of_client are wrong:
cat zones/client_of_client.test.lan.conf
object Zone "client_of_client.test.lan" {
endpoints = [ "client.test.lan" ]
parent = "master.test.lan"
}
As you can see the parent is wrong. The hostcheck of the host is also wrong:
cat hosts/client_of_client.test.lan.conf :(
object Host "client_of_client.test.lan" {
import "satellite-host"
check_command = "cluster-zone"
}
The check_command is set to cluster-zone, which has the consequence that the hostcheck is always red. Dummy or something similar would work.
Parent Task: #13257
Relations:
The text was updated successfully, but these errors were encountered: