Closed widhalmt closed 4 years ago
@widhalmt: related to this problem there will be https://github.com/Icinga/icingaweb2-module-director/issues/1958 in v1.7.
Cheers, Thomas
Thanks @Thomas-Gelf . That's great to hear. We'll add the check to diagnostics because some users will have this kind of configuration without Director, too.
Icinga 2 2.11 prohibits a configuration which was never correct but did work because of config checks not so strict. Because this could lead to problems the new release of Icinga doesn't allow this anymore.
What's it all about: Zone objects for satellites or Agents which are not mere command_endpoints could be configured in
/etc/icinga2/zones.d/[parent zone]
and were synced to other masters and satellites inparent zone
. From 2.11 on the Zone objects have to be configured outsidezones.d
, namely inzones.conf
.There's an issue explaining the topic in more detail and trying to find a solution which works with the new fixes and maybe old configuration as well: https://github.com/Icinga/icinga2/issues/7530
We need a way to detect zones which are configured in a subdirectory of
zones.d
and have their own config.