Bug 1602001

Summary:	cannot add cenotaph in read only consumer
Product:	Red Hat Enterprise Linux 7	Reporter:	German Parente <gparente>
Component:	389-ds-base	Assignee:	Ludwig <lkrispen>
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	high	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	high
Version:	7.6	CC:	aadhikar, cpelland, gerald.prock, lkrispen, mreynolds, msauton, nkinder, pasik, rmeggins, tmihinto, tscherf, vashirov, winstan
Target Milestone:	rc	Keywords:	ZStream
Target Release:	7.7
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	389-ds-base-1.3.9.1-1.el7	Doc Type:	Bug Fix
Doc Text:	.Replicating `modrdn` operations to read-only Directory Server now succeeds The conflict entry management in Directory Server requires to add tracking entries for `modrdn` operations. Previously, adding these entries failed on read-only consumers and, as a consequence, `modrdn` operations could not be replicated to such instances. This update fixes the problem. As a result, replicating `modrdn` operations to read-only consumers succeeds.	Story Points:	---
Clone Of:
Clones:	1672179 (view as bug list)		Environment:
Last Closed:	2019-08-06 12:58:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1644708, 1647919, 1672179

Description German Parente 2018-07-17 14:58:24 UTC

Description of problem:

We can see these sort of errors in read only consumer:

[17/Jul/2018:08:13:02.498430580 -0500] - ERR - conn=XXXX op=YY csn=<some csn> - urp_fixup_add_cenotaph - failed to add cenotaph, err= 10

the conflict should not fail by referral and should be created in any case in read only consumer.

Version-Release number of selected component (if applicable): 389-ds-base-1.3.7.5-21.el7_5.x86_64

This seems similar to 

https://pagure.io/389-ds-base/issue/49623

since the operation that are provoking this error are MODRDN's.

Comment 2 Ludwig 2018-12-06 12:31:09 UTC

created ticket 50078, the issue is different from 49623

Comment 5 Akshay Adhikari 2019-04-30 10:55:20 UTC

[root@rhel7-aadhikar1 dirsrvtests]# py.test tests/tickets/ticket50078_test.py 
============================================================================ test session starts ============================================================================
platform linux -- Python 3.6.3, pytest-4.4.0, py-1.8.0, pluggy-0.9.0
389-ds-base: 1.3.9.1-5.el7
nss: 3.43.0-6.el7
nspr: 4.21.0-1.el7
openldap: 2.4.44-21.el7_6
cyrus-sasl: 2.1.26-23.el7
FIPS: disabled
rootdir: /root/389-ds-base/dirsrvtests
plugins: metadata-1.8.0, html-1.20.0
collected 1 item                                                                                                                                                            

tests/tickets/ticket50078_test.py .                                                                                                                                   [100%]
....

=================================================================== 1 passed in 62.15 seconds 
===================================================================

Marking as VERIFIED.

Comment 11 errata-xmlrpc 2019-08-06 12:58:42 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, 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/RHBA-2019:2152