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 1600631 - In repicated topology a single-valued attribute can diverge
Summary: In repicated topology a single-valued attribute can diverge
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.7
Assignee: thierry bordaz
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-12 16:08 UTC by mreynolds
Modified: 2020-09-13 22:09 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.3.9.1-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Cause: For single value attribute, URP (update replication protocol) can assign different value to the attribute depending on the order of the updates Consequence: an attribute of the same entry can have different value on some DS instances even when the instances are in sync. Fix: rewrite the entry state resolution for single value attribute. Result: all DS instances select the same value of a single value attribute
Clone Of:
Environment:
Last Closed: 2019-08-06 12:58:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 2717 0 None None None 2020-09-13 22:09:31 UTC
Red Hat Product Errata RHBA-2019:2152 0 None None None 2019-08-06 12:59:00 UTC

Description mreynolds 2018-07-12 16:08:33 UTC 
This bug is created as a clone of upstream ticket:
https://pagure.io/389-ds-base/issue/49658

#### Issue Description
On a replicated topology with more than 2 server, a single value attribute can be present (with a given value) on some instances and can be deleted on some others.

This happens if several update lead to the same value of the attribute but are replicated in a different order.


#### Package Version and Platform
At least since 1.3.7


#### Steps to reproduce

Testcase provided

#### Actual results
The attribute can be deleted or present depending of the server


#### Expected results
The attribute value should be identical on all servers
Comment 3 thierry bordaz 2019-02-05 15:11:06 UTC 
The ticket is pushed upsteam https://pagure.io/389-ds-base/issue/49658 --> POST
Comment 5 Akshay Adhikari 2019-04-30 11:35:55 UTC 
[root@rhel7-aadhikar1 dirsrvtests]# py.test tests/tickets/ticket49658_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 36 items                                                                                                                                                          

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

================================================================ 36 passed 1359.35 seconds ================================================================

Marking this as VERIFIED.
Comment 7 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
Note You need to log in before you can comment on or make changes to this bug.