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 1904347 - Entries conflict not resolved by replication [rhel-8.3.0.z]
Summary: Entries conflict not resolved by replication [rhel-8.3.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 8.0
Assignee: thierry bordaz
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On: 1898850
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-04 07:54 UTC by RHEL Program Management Team
Modified: 2021-04-06 14:33 UTC (History)
6 users (show)

Fixed In Version: 389-ds-devel-1.4-8030020201203210520.e114a9e7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1898850
Environment:
Last Closed: 2020-12-15 17:12:41 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)

Comment 4 sgouvern 2020-12-04 15:03:55 UTC 
With build 389-ds-base-1.4.3.8-6.module+el8.3.0+8995+c08169ba.x86_64

# PYTHONPATH=src/lib389/ py.test -s -v dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_complex_add_modify_modrdn_delete
re-exec with libfaketime dependencies
================================================== test session starts ==================================================
platform linux -- Python 3.6.8, pytest-6.1.2, py-1.9.0, pluggy-0.13.1 -- /usr/bin/python3.6
cachedir: .pytest_cache
metadata: {'Python': '3.6.8', 'Platform': 'Linux-4.18.0-240.el8.x86_64-x86_64-with-redhat-8.3-Ootpa', 'Packages': {'pytest': '6.1.2', 'py': '1.9.0', 'pluggy': '0.13.1'}, 'Plugins': {'metadata': '1.11.0', 'html': '3.1.0', 'libfaketime': '0.1.2'}}
389-ds-base: 1.4.3.8-6.module+el8.3.0+8995+c08169ba
nss: 3.53.1-11.el8_2
nspr: 4.25.0-2.el8_2
openldap: 2.4.46-15.el8
cyrus-sasl: 2.1.27-5.el8
FIPS: disabled
rootdir: /mnt/tests/rhds/tests/upstream/ds/dirsrvtests, configfile: pytest.ini
plugins: metadata-1.11.0, html-3.1.0, libfaketime-0.1.2
collected 1 item                                                                                                        

dirsrvtests/tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_complex_add_modify_modrdn_delete INFO:lib389.topologies:Instance with parameters {'ldap-port': 39001, 'ldap-secureport': 63701, 'server-id': 'master1', 'suffix': 'dc=example,dc=com'} was created.
INFO:lib389.topologies:Instance with parameters {'ldap-port': 39002, 'ldap-secureport': 63702, 'server-id': 'master2', 'suffix': 'dc=example,dc=com'} was created.
INFO:lib389.topologies:Creating replication topology.
INFO:lib389.topologies:Joining master master2 to master1 ...
INFO:lib389.replica:SUCCESS: bootstrap to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 completed
INFO:lib389.replica:SUCCESS: Agreement from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 is was created
INFO:lib389.replica:SUCCESS: Agreement from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 is was created
INFO:lib389.replica:SUCCESS: Replication from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 is working
INFO:lib389.replica:SUCCESS: Replication from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 is working
INFO:lib389.replica:SUCCESS: joined master from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002
INFO:lib389.topologies:Ensuring master master1 to master2 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 already exists
INFO:lib389.topologies:Ensuring master master2 to master1 ...
INFO:lib389.replica:SUCCESS: Agreement from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 already exists
INFO:lib389.replica:SUCCESS: Replication from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 is working
INFO:dirsrvtests.tests.suites.replication.conflict_resolve_test:Test add-del on M1 and add on M2
INFO:dirsrvtests.tests.suites.replication.conflict_resolve_test:Test add-mod on M1 and add on M2
INFO:dirsrvtests.tests.suites.replication.conflict_resolve_test:Test add-modrdn on M1 and add on M2
INFO:dirsrvtests.tests.suites.replication.conflict_resolve_test:Test multiple add, modrdn
INFO:dirsrvtests.tests.suites.replication.conflict_resolve_test:Add - del on both masters
INFO:dirsrvtests.tests.suites.replication.conflict_resolve_test:Test modrdn - modrdn
INFO:dirsrvtests.tests.suites.replication.conflict_resolve_test:Test modrdn - del
INFO:lib389.replica:SUCCESS: Replication from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 is working
INFO:lib389.replica:SUCCESS: Replication from ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39002 to ldap://ci-vm-10-0-138-217.hosted.upshift.rdu2.redhat.com:39001 is working
PASSEDInstance slapd-master1 removed.
Instance slapd-master2 removed.


=================================================== warnings summary ====================================================
tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_complex_add_modify_modrdn_delete
  /mnt/tests/rhds/tests/upstream/ds/src/lib389/lib389/__init__.py:141: DeprecationWarning: Use of raw ldap function search_s. This will be removed in a future release. Found in: /mnt/tests/rhds/tests/upstream/ds/dirsrvtests/tests/suites/replication/conflict_resolve_test.py:135
    "Found in: %s:%s" % (name, frame.filename, frame.lineno)))

tests/suites/replication/conflict_resolve_test.py::TestTwoMasters::test_complex_add_modify_modrdn_delete
  /mnt/tests/rhds/tests/upstream/ds/src/lib389/lib389/__init__.py:141: DeprecationWarning: Use of raw ldap function search_ext_s. This will be removed in a future release. Found in: /usr/local/lib64/python3.6/site-packages/ldap/ldapobject.py:870
    "Found in: %s:%s" % (name, frame.filename, frame.lineno)))

-- Docs: https://docs.pytest.org/en/stable/warnings.html
======================================= 1 passed, 2 warnings in 239.24s (0:03:59) =======================================


-> marking as verified
Comment 9 errata-xmlrpc 2020-12-15 17:12:41 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:1.4 bug fix 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:5505
Note You need to log in before you can comment on or make changes to this bug.