Description of problem: ERR - repl_version_plugin_recv_acquire_cb - [file ipa_repl_version.c, line 119]: Incompatible IPA versions, pausing replication
Version-Release number of selected component (if applicable):
package samba is not installed
Steps to Reproduce:
1. Install Master and setup replica.
2. Check the error log on dirsrv
[28/Aug/2018:17:25:47.177325169 +051800] - ERR - repl_version_plugin_recv_acquire_cb - [file ipa_repl_version.c, line 119]: Incompatible IPA versions, pausing replication. This server: "20100614120000" remote server: "(null)".
Expected results: Incompatible IPA version, pausing replication looks to me as an incorrect error message since we are using the same version of IPA across replica and master, hence this needs to be solved to avoid confusion.
The problem seems to be systematic
It happens on installed replica not on the master.
It happens during the step "setting up initial replication" (_setup_replica)
It calls replication.enable_replication_version_checking that enables the plugin "IPA Version Replication"
The replication session start with an extop. On the supplier side, the plugin "cn=IPA Version Replication,cn=plugins,cn=config" adds a payload to the extop. On the consumer side extop is decoded and payload is compared to an expected value.
If the value is not the expected one, total update fails and incremental update backoff. In short replication is broken.
The plugin is by default disabled on master and enabled on consumer.
That means the consumer will add/check a valid payload, while the master adds invalid payload and enable to check payload (if it checks).
If we want to keep replication version check this plugin needs to be enabled on both sides (master and replicas).
The workaround (and fix) is to disable it on replicas as well (enable_replication_version_checking should set 'enabledPlugin: off')