Bug 1876028

Summary:	errors log with incorrectly formatted message parent_update_on_childchange on PARENTUPDATE_DEL
Product:	Red Hat Enterprise Linux 7	Reporter:	Marc Sauton <msauton>
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.8	CC:	bsmejkal, kbanerje, kurathod, pasik, rcain, sgouvern, spichugi, tbordaz, vashirov
Target Milestone:	rc	Keywords:	TestCannotAutomate
Target Release:	7.9
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.10.2-7.1.el7_9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-10 13:14:10 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:

Description Marc Sauton 2020-09-05 00:30:35 UTC

Description of problem:

there is a apparent incorrectly formatted error message
ERR - parent_update_on_childchange - Parent %s has no children. (op 0x%x, repl_op 0x%x)

the variables are not interpreted, and strangely, the next error message is appended, like if there was a missing carriage return, although there is clearly one in the code, in 
./ldap/servers/slapd/back-ldbm/parents.c

the parameters seem valid, but is cannot access//read slapi_entry_get_dn because it was deleted? ( may be a side effect of an unexpected error 1 in this example.)
but then why the \n would not be applied?

note this was with 389-ds-base-1.3.10.1-14.el7_8 , but on RHEL-7.4 instead of the tested RHEL-7.8


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

389-ds-base-1.3.10.1-14.el7_8.x86_64
RHEL-7.4


How reproducible:
N/A
happened several times in a customer environment

Steps to Reproduce:
1. N/A
2.
3.

Actual results:


access (edited)
[03/Sep/2020:20:09:24.278074084 +0300] conn=73050 op=66 DEL dn="cn=entry1,dc=example,dc=test"
[03/Sep/2020:20:09:24.290704098 +0300] conn=73050 op=66 RESULT err=1 tag=107 nentries=0 etime=0.012822845 csn=5f514d70000000100000

errors (edited)
[03/Sep/2020:20:09:24.278184398 +0300] - DEBUG - NSMMReplicationPlugin - ruv_add_csn_inprogress - Successfully inserted csn 5f514d70000000100000 into pending list
[03/Sep/2020:20:09:24.280256804 +0300] - ERR - parent_update_on_childchange - Parent %s has no children. (op 0x%x, repl_op 0x%x) 
 - cn=entry1,dc=example,dc=test[03/Sep/2020:20:09:24.281661564 +0300] - ERR - ldbm_back_delete - conn=73050 op=66 parent_update_on_childchange: old_entry=0x0x55807bbc6460, new_entry=0x(nil), rc=-1
[03/Sep/2020:20:09:24.289188838 +0300] - DEBUG - replication - multimaster_mmr_postop - error 0 for oparation 563.
[03/Sep/2020:20:09:24.290765002 +0300] - DEBUG - NSMMReplicationPlugin - process postop - conn=73050 op=66 csn=5f514d70000000100000 canceling operation csn
[03/Sep/2020:20:09:24.292106631 +0300] - ERR - NSMMReplicationPlugin - process_postop - Failed to apply update (5f514d70000000100000) error (1).  Aborting replication session(conn=73050 op=66)


Expected results:


Additional info:

Comment 6 mreynolds 2020-10-20 18:52:49 UTC

Upstream ticket:
https://github.com/389ds/389-ds-base/issues/4389

Comment 11 bsmejkal 2020-10-26 10:08:45 UTC

Patch for the 389-ds-base-1.3.10.2-7.1.el7_9 is present and is correctly applied. 
Marking as VERIFIED, SanityOnly.

Comment 15 errata-xmlrpc 2020-11-10 13:14:10 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-base 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/RHBA-2020:5041

Comment 16 Red Hat Bugzilla 2023-09-18 00:22:19 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days