Bug 1074076

Summary:	e_uniqueid fails to set if an entry is a conflict entry
Product:	Red Hat Enterprise Linux 6	Reporter:	Noriko Hosoi <nhosoi>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED ERRATA	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	jgalipea, mkubik, nkinder
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-34.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-14 07:53:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Noriko Hosoi 2014-03-07 21:18:46 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47735

When an entry is turned to be a conflict entry, its nsUniqueId has a mdcsn info as a subtype like this:
 nsUniqueId;mdcsn-5319136f000200010000: c5e0d787-a58f11e3-b7f9dfd1-acc3d5e4

In this case, the attribute type is assigned to the berval "type" as follows:
 type.bv_val = "nsUniqueId;mdcsn-5319136f000200010000"
 type.bv_len = 37

The subtyped stateinfo is processed in str2entry_state_information_from_type, which modifies type.bv_val to "nsUniqueId", but type.bv_len remains 37.

str2entry_fast has this logic to set e_uniqueid, where the nsUniqueId with stateinfo fails to set the value to e_uniqueid.
if ( type.bv_len == 10 && PL_strncasecmp (type.bv_val, "nsUniqueId", type.bv_len) == 0 ){

Comment 2 Noriko Hosoi 2014-06-18 23:52:23 UTC

This test case covers this bug, as well.

https://bugzilla.redhat.com/show_bug.cgi?id=1080185#c1

Comment 3 Noriko Hosoi 2014-06-19 00:08:33 UTC

(In reply to Noriko Hosoi from comment #2)
> This test case covers this bug, as well.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1080185#c1

Once the test is done, search conflict entries and check that nsUniqueId attribute exists in each entry.

Note: a conflict entry looks like this:
   dn: nsuniqueid=<UNIQID>+<RDN>,<PARENTDN>
   [...]
   nsds5ReplConflict: namingConflict <DN>

Comment 5 errata-xmlrpc 2014-10-14 07:53:27 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.

http://rhn.redhat.com/errata/RHBA-2014-1385.html