-
Notifications
You must be signed in to change notification settings - Fork 202
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
Change Cluster Zones In ServiceSet #1589
Milestone
Comments
+1 |
+1 |
1 similar comment
+1 |
+1 |
ref/NC/761567 |
ref/NC/767217 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are using a Icinga HA Configuration with 2 Master-Nodes, 2 satellite in the network zone and 2 satellite in the server zone.
We do our full configuration with the director. We also use service sets to configure services. We saw that every service set is saved in the file /var/lib/icinga2/api/zones/director-global/director/servicesets.conf. So that means that every node gets the apply rules from the service set. So when a set is for example only for servers also the network nodes gets this rules. And of course and vice versa.
The result is that one node can't find the host which is in the other Zone. And if you make a icinga2 daemon -C then you will get a lot of warnings and of course you can find that also in the icinga2 log file after deployment. And the last point let the log file growing for nothing.
A solution could be to set a zone at the service set like at other config sites like dependencys, templates, checks etc. Because if I changed the Zone in the templates (service or command) nothing changed in this case.
Your Environment
icinga2 --version
): r2.9.1-1The text was updated successfully, but these errors were encountered: