...
During activation of changes from master for a remote site, we faced an issue. This will haven hapen if WATO is enabled on a the remote site and if you have pending changes there.
Info |
---|
On the slave:
In the 'replication_changes_slave.mk' you will find the pending change.
Info | ||
---|---|---|
| ||
OMD[slave]:~/var/check_mk/wato$ ll |
...
Code Block | ||
---|---|---|
| ||
OMD[slave]:~/var/check_mk/wato$ cat replication_status_slave.mk {'current_activation': None, 'last_activation': 'f9607439-2303-412c-a188-f4e0f54702ae', 'times': {'restart': 1.6235217094421388}} OMD[slave]:~/var/check_mk/wato$ cat replication_changes_slave.mk {'need_restart': True, 'need_sync': True, 'user_id': u'cmkadmin', 'time': 1607689496.047742, 'domains': ['check_mk'], 'text': u'Modified host p19master-vcenter-agent.txt.', 'object': ('CREHost', 'p19master-vcenter-agent.txt'), 'id': 'cc91dcc8-bcc6-46fa-a264-9bdc5b041720', 'action_name': 'edit-host'} |
...
Solution
In order to activate changes successfully from master to slave, you need to delete both replication-Files on the slave:
...
Note |
---|
To avoid this kind of issue, you should disable WATO an on the slave and push the configuration only from master. |
...