Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #10980] icinga2 node update-config does not work well with indirect connected zones #3849
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
I have the following setup
master <- client <- client_of_client where "client_of_client" is connected via client to my master instance.
Unfortunately the generated configuration files for the client_of_client are wrong:
As you can see the parent is wrong. The hostcheck of the host is also wrong:
cat hosts/client_of_client.test.lan.conf :(
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
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.