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.

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 ){

Note: this is a regression introduced in RHEL-7.0 by Bug 1032318 - entries with empty objectclass attribute value can be hidden

Hi Noriko, requesting you to add steps to reproduce.

(In reply to Sankar Ramalingam from comment #1)
> Hi Noriko, requesting you to add steps to reproduce.

Set up MMR.
Repeat adding and deleting the same entry on each master to generate a conflict entry.
Run search the entry in parallel.

It used to crash the server.

*** Bug 1076191 has been marked as a duplicate of this bug. ***

Fixed the Intex failure in 389-ds-base-1.3.1.6-24.el7

(In reply to Noriko Hosoi from comment #5)
> Fixed the Intex failure in 389-ds-base-1.3.1.6-24.el7

^Intex^Index^, of course...

While running on the newest build the scenario from #2, this happened
http://pastebin.test.redhat.com/197477

Is this some known defect or a new bug/regression?

(In reply to Milan Kubík from comment #7)
> While running on the newest build the scenario from #2, this happened
> http://pastebin.test.redhat.com/197477
> 
> Is this some known defect or a new bug/regression?

Thank you for retesting the new build, Milan.  I believe this is a new bug.  If e_uniqueid is not set, it crashes the server.

Could you open a new bug and set the target to 7.1?  Thanks!!

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.