Red Hat Directory Server crash on tombstone entry modify with new superior entry

Solution Unverified - Updated -

Issue

An inconsistent behavior and results of MODRDN operations when processing a tombstone entry caused the Red Hat Directory Server / RHDS to terminate unexpectedly, in the following scenario:

deleteoldrdn: 0 newsuperior: <dn>

The crash had the side effect, that the entry was no longer accessable after restart, an attempt to repeat the operation would return a err=32 (no such object).

Environment

Red Hat Directory Server 9 on RHEL 6:

389-ds-base-1.2.11.15-14.el6_4.x86_64
redhat-ds-base-9.0.0-0.17.el6dsrv.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content