[Freeipa-devel] [PATCH] 1072 enable transaction support

[Nalin Dahyabhai]

On Tue, Nov 20, 2012 at 02:08:04PM +0100, Martin Kosek wrote:
> 4) nsslapd-pluginbetxn is not set for schema compatibility plugin after upgrade:
> 
> # Schema Compatibility, plugins, config
> dn: cn=Schema Compatibility,cn=plugins,cn=config
> nsslapd-pluginId: schema-compat-plugin
> cn: Schema Compatibility
> objectClass: top
> objectClass: nsSlapdPlugin
> objectClass: extensibleObject
> nsslapd-pluginDescription: Schema Compatibility Plugin
> nsslapd-pluginEnabled: on
> nsslapd-pluginPath: /usr/lib64/dirsrv/plugins/schemacompat-plugin.so
> nsslapd-pluginVersion: 0.44 (betxn support available and enabled by default)
> nsslapd-pluginVendor: redhat.com
> nsslapd-pluginType: object
> nsslapd-pluginInitfunc: schema_compat_plugin_init
> 
> This is supposed to be enabled by default, judging by nsslapd-pluginVersion
> description, but this may create an inconsistency between new installs and
> upgraded IPA servers.
> 
> The same issue applies to IPA server with NIS plugin enabled.

Which version of IPA is it that starts explicitly configuring
"nsslapd-pluginbetxn" values for plugins?

For Fedora, at least, are there cases where we're going from a version
that didn't configure that setting to a version that does configure it,
as an update within a single release?  If not, I can make the default
change depending on which release we're building for, and we'll be fine.
If that sort of upgrade is expected, though, the package will probably
need to start conflicting with versions of IPA that don't configure
"nsslapd-pluginbetxn" one way or the other, because there's no default
value that's guaranteed to be safe.

Nalin