Description
When adding new rules to e.g. checkmk_server__site_cfg_rules they are properly configured for a master site, but if it has some slave sites they won't be automatically synchronized to the slave sites. The same issue exists for all site configurations done to a distributed setup by this Ansible role.
The problem is, that Check_MK itself doesn't know about the updated rules and therefore won't trigger its built-in synchronization mechanism. Unfortunately there is no API call which can trigger this synchronization. A possible solution for this issue is to create an Ansible task which would rsync the rule configuration files (e.g. rules.mk) to the appropriate slave sites. However, there are currently not enough information available to the master server on how to reach a slave server via Ansible.
Work-around: After updating the monitoring rules via Ansible, login to WATO, click edit on a monitoring rule, save it without modification and then apply the change. This will push the master site configuration to all slave sites.