RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
While slapi-nis supports working with the directory server's backend transaction scheme, it does so by checking at build-time if the server supports them.  At the time we built slapi-nis-0.40-1.el6, we built it against 389-ds-base-1.2.9.14-1.el6_2.2, so transaction support was not built in.

We need to add explicit versioned build and install-time dependencies to the package, and then recompile it.

Version-Release number of selected component (if applicable):
slapi-nis-0.40-1.el6

The strategy which directory server will be taking for transaction support changed since transaction support was added to the plugin -- the new strategy assumes that plugins remain unaware of transactions, so we actually need to ensure that support in the plugin for transactions is either disabled or excised.

lowering priority - it was already verified in 6.3 but had to be committed to both branches (6.4)

Ran regression tests for IPA. No issues found. Marking this verified - Sanity only

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0370.html