1790986 – cenotaph errors on modrdn operations

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.

Bug 1790986 - cenotaph errors on modrdn operations

Summary: cenotaph errors on modrdn operations

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	389-ds-base
Sub Component:
Version:	8.2
Hardware:	All
OS:	Linux
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	8.0
Assignee:	mreynolds
QA Contact:	RHDS QE
Docs Contact:
URL:
Whiteboard:
Depends On:	1762901
Blocks:
TreeView+	depends on / blocked

Reported:	2020-01-14 16:10 UTC by mreynolds
Modified:	2020-11-04 03:08 UTC (History)
CC List:	10 users (show)
Fixed In Version:	389-ds-base-1.4.3.8-2.module+el8.3.0+6591+ebfc9766
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	1762901
Environment:
Last Closed:	2020-11-04 03:07:24 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2020:4695	0	None	None	None	2020-11-04 03:07:38 UTC

Description mreynolds 2020-01-14 16:10:41 UTC

+++ This bug was initially created as a clone of Bug #1762901 +++

Description of problem:

can probably be ignored as MODRDN succeeds, but trace of "urp_fixup_add_cenotaph - failed to add cenotaph, err= 68"
the errors log file can be filled with thois message.

duplicated from upstream ticket number 49623
https://pagure.io/389-ds-base/issue/49623

"
Doing a modrdn (new superior) on a standalone plain instance (no replication setup) I see:

[23/Mar/2018:08:34:17.112762032 -0400] - ERR - conn=11 op=11 - urp_fixup_add_cenotaph - failed to add cenotaph, err= 21

I see the same error if I move it back and forth between subtrees.

If I enable replication, and delete an entry then recreate it, and do a modrdn back and forth (twice) between two subtrees I see:

[23/Mar/2018:08:39:45.077620637 -0400] - ERR - conn=11 op=75 csn=5ab4f591000000030000 - urp_fixup_add_cenotaph - failed to add cenotaph, err= 68

--> This one is a little trickier to reproduce. It requires deleting and readding the same entry and moving it back a forth a few times, but eventually you will get the error above.
"

pls comment from Ludwig K. / lkrispen
"
Ok, I reproduced this again. The problem is that the dn of the cenotaph is built by creatin a new rdn of

 nsuniqueid=nnnnn-nnnnn-nnnnn-nnnnn+<old rdn>

If the entry is moved back and forth between subtrees, when it is moved the second time from the same subtree will generate a dn which already exists and so the new cenotaph cannot be added.
The original MODRDN succeeds, so only a potential use in conflict resolution could be an issue, but in a usual deployment it should have no effect other than the message in theerror log
"


Version-Release number of selected component (if applicable):

RHEL-7.6 with 389-ds-base-1.3.8.4-25.1.el7_6.x86_64
trying to reproduce on RHEL-7.7 with 389-ds-base-1.3.9.1-10.el7


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from RHEL Program Management on 2019-10-17 18:49:12 UTC ---

Since this bug report was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Marc Sauton on 2019-10-17 18:51:51 UTC ---

Linking bugzilla 1762901 and salesforce case number 02486369 for tirol.gv.at

Thanks Ludwig for the update in the upstream ticket at https://pagure.io/389-ds-base/issue/49623#comment-605445

--- Additional comment from Marc Sauton on 2019-11-14 01:18:57 UTC ---

near same scenario as open ticket 49623 cenotaph errors on modrdn operations
- different errors from upstream ticket
  https://pagure.io/389-ds-base/issue/49623
- different from bz 1602001 - cannot add cenotaph in read only consumer
  https://bugzilla.redhat.com/1602001
  that was fixed in 389-ds-base-1.3.9.1-1.el7

Comment 4 Akshay Adhikari 2020-06-23 15:11:47 UTC

============================================================================ test session starts =================================================================
platform linux -- Python 3.6.8, pytest-5.4.3, py-1.8.1, pluggy-0.13.1 -- /usr/bin/python3.6
cachedir: .pytest_cache
metadata: {'Python': '3.6.8', 'Platform': 'Linux-4.18.0-211.el8.x86_64-x86_64-with-redhat-8.3-Ootpa', 'Packages': {'pytest': '5.4.3', 'py': '1.8.1', 'pluggy': '0.13.1'}, 'Plugins': {'metadata': '1.9.0', 'html': '2.1.1'}}
389-ds-base: 1.4.3.8-3.module+el8.3.0+6935+6f68b788
nss: 3.44.0-15.el8
nspr: 4.21.0-2.el8_0
openldap: 2.4.46-11.el8
cyrus-sasl: not installed
FIPS: disabled
rootdir: /workspace/ds/dirsrvtests, inifile: pytest.ini
plugins: metadata-1.9.0, html-2.1.1
collected 1 item                                                                                                                                                            

dirsrvtests/tests/tickets/ticket49623_2_test.py::test_modrdn_loop PASSED                                                                                              [100%]

============================================================================= 1 passed in 7.92s ==================================================================

Marking it as VERIFIED.

Comment 8 errata-xmlrpc 2020-11-04 03:07:24 UTC

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 (389-ds:1.4 bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2020:4695

Note You need to log in before you can comment on or make changes to this bug.