#49615 dn of nested tombstones is incorrect
Opened a year ago by lkrispen. Modified a year ago

Issue Description

If nested entries are deleted the dns of the lower level entries are incorrect.

eg if we have

dn: <suffix>

dn: cn=parent,<suffix>

dn: cn=child,cn=parent,<suffix>

and then delete child and the parent the resulting tombstones are:

dn: nsuniqueid=xxxxx,cn=parent,<suffix>
dn: nsuniqueid=yyyyy,cn=child,cn=parent,<suffix>

although the dn of the child should be:
dn: nsuniqueid=yyyyy,cn=child,nsuniqueid=xxxxx,cn=parent,<suffix>

NOTE: the correct tombstone dns are difficult to view, since the rdns are bloated, correct rdns should follow ticket #49507


Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.3.7.0

a year ago

Login to comment on this ticket.

Metadata