Due to possible plug-in interaction issues, we should evaluate the order that IPA SLAPI plug-ins should be executed. Currently, most plug-ins do not specify a precedence, so they are all at a level of 50. The execution occurs alphabetically within a given plug-in type (though DS does not guarantee this). We should really be setting explicit values for all of the IPA plug-ins since so many SLAPI plug-ins are used within IPA.
As an example, we recently found that the ipa-modrdn plug-in would cause odd issues with the managed entries plug-in my performing an internal modify operation before the MODRDN was picked up by the managed entries plug-in. Changing the precedence of ipa-modrdn to 60 fixed this issue. More issues like this may be out there.
Bug that triggered the ticket. https://bugzilla.redhat.com/show_bug.cgi?id=715112
The ticket is actually wider in scope than the original bug.
Looks like only the Retro Changelog Plugin plugin defines nsslapd-pluginPrecedence
The ds team determined that the precedence is getting set in the wrong entry. It should be getting set in cn=IPA MODRDN,cn=plugins,cn=config instead
put precedence in the right place
Metadata Update from @nkinder:
- Issue assigned to rcritten
- Issue set to the milestone: FreeIPA 2.1.2 (bug fixing)
to comment on this ticket.