#8799 Remove DS problematic code
Closed: fixed by abbra. Opened by mreynolds.

Request for enhancement

In Directory Server we are replacing "master" with "supplier" for the replication plugin. The following references to the plugin name need to be changed:

daemons/ipa-slapi-plugins/ipa-version/version-conf.ldif:nsslapd-plugin-depends-on-named: Multimaster Replication Plugin
daemons/ipa-slapi-plugins/topology/ipa-topology-conf.ldif:nsslapd-plugin-depends-on-named: Multimaster Replication Plugin
install/updates/20-enable_dirsrv_plugins.update:# Multimaster Replication Plugin, plugins, config
install/updates/20-enable_dirsrv_plugins.update:dn: cn=Multimaster Replication Plugin,cn=plugins,cn=config
install/updates/10-enable-betxn.update:dn: cn=Multimaster Replication Plugin,cn=plugins,cn=config
install/updates/20-replication.update:default: nsslapd-plugin-depends-on-named: Multimaster Replication Plugin
ipaserver/install/replication.py:            DN(('cn', 'Multimaster Replication Plugin'), ('cn', 'plugins'),
ipatests/test_ipaserver/test_topology_plugin.py:                [u'Multimaster Replication Plugin', u'ldbm database'],

Thanks @mreynolds for the heads-up. We already adapted one healthcheck test in ebf9285 ipatests: update expected message, but for this ticket we will need to synchronize more closely with 389-ds.

Are all the changes already present in the PR https://github.com/389ds/389-ds-base/pull/4720 ? If that's the case we will be able to test in our nightlies when the 389-ds PR gets merged, using @389ds/389-ds-base-nightly copr repo. Note that the tests only exercise new installations, not upgrades.
The easiest way will be to bump our Requires on ds, but will the update of 389ds packages fix the configuration or is it something we need to plan on our side?

I have a FreeIPA PR for this as well, but the work in 389ds is not done yet so I have not filed it.

I am working on a upgrade solution in DS to handle the renaming of the replication plugin. Once that is done and tested then we can look at how to synchronize our releases.

master:

  • b4b2c10e234315042b54a4556bf264d55ecd07c9 ds: Support renaming of a replication plugin in 389-ds

ipa-4-9:

  • 04a6583ce3c1304907d092b19e5c7cc915f6952a ds: Support renaming of a replication plugin in 389-ds

Metadata Update from @abbra:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

ipa-4-8:

  • 02845bece6f9483dfc8d8d1d4b1ba046672caa91 ds: Support renaming of a replication plugin in 389-ds
  • ebeb4980360e3b13c021de9afb6c46651d88343c Use get_replication_plugin_name in LDAP updater
Metadata