Bug 1439340

Description of problem:

IPA LDAP server replication plug-in
cn=IPA Version Replication,cn=plugins,cn=config
/usr/lib64/dirsrv/plugins/libipa_repl_version.so

https://pagure.io/freeipa/issue/6847

we have seen those errors a few times in several cases on RHEL-7.3 in the LDAP server errors log file without any other event when replication verbose log is disabled:

[28/Mar/2017:22:42:30 764332032 -0700] repl_version_plugin_recv_acquire_cb - [file ipa_repl_version.c, line 119]: Incompatible IPA versions, pausing replication. This server: 20100614120000" remote server: "(null)".

per
./daemons/ipa-slapi-plugins/ipa-version/ipa_repl_version.c
it seem like a replica would go in incremental backoff mode, after a replication session failure, so it would not be a fatal replication session error.

    This is called on a replica when it receives a start replication
    extended operation from a master.
    *
    The data sent by the master (version) is compared with our own
    hardcoded version to determine if replication can proceed or not.
    *
    The replication plug-in will take care of freeing data_guid and data.
    *
    Returning non-0 will abort the replication session. This
    results in the master going into incremental backoff mode.
    /
    static int
    repl_version_plugin_recv_acquire_cb(const char repl_subtree, int is_total,
    const char data_guid, const struct berval data)
    {

the root cause seem to be with a hardcoded data version value in the plug-in
./daemons/ipa-version.h
define DATA_VERSION 20100614120000

Although this does not seem to be a fatal error in all the replication sessions, it is seen as a fatal error in the IPA replication plug-in:
./daemons/ipa-slapi-plugins/ipa-version/ipa_repl_version.c

    if (!(strcmp(data_version, data->bv_val) == 0)) {
        LOG_FATAL("Incompatible IPA versions, pausing replication. "
                  "This server: \"%s\" remote server: \"%s\".\n",
                  data_version, data->bv_val);
        return 1;

Although this may be ignored, I am not sure what may be the effect of not having a full init and only incremental updates, we need at least one full init a first time.
We should probably fix this so there are no suspicious important LDAP replication error messages with an outdated timestamp in years and a null value of a remote server.
LDAP replication is critical, and this would help clear false positives when trying to troubleshoot replication issues.


Version-Release number of selected component (if applicable):

389-ds-base-1.3.5.10-15.el7_3.x86_64
ipa-server-4.4.0-14.el7_3.4.x86_64
redhat-release-server-7.3-7.el7.x86_64


How reproducible:
N/A

Steps to Reproduce:
1. N/A
2.
3.

Actual results:


Expected results:


Additional info: