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 2236163 - Regression: replication can't be enabled for consumer or hub role
Summary: Regression: replication can't be enabled for consumer or hub role
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: 389-ds-base
Version: 9.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Simon Pichugin
QA Contact: LDAP QA Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-30 13:53 UTC by Viktor Ashirov
Modified: 2023-11-07 09:09 UTC (History)
7 users (show)

Fixed In Version: 389-ds-base-2.3.6-3.el9_3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:25:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 5848 0 None closed dsconf should prevent setting the replicaID for hub and consumer roles 2023-09-01 02:02:27 UTC
Red Hat Issue Tracker IDMDS-3597 0 None None None 2023-08-30 16:24:52 UTC
Red Hat Issue Tracker RHELPLAN-166985 0 None None None 2023-08-30 14:58:01 UTC
Red Hat Product Errata RHBA-2023:6350 0 None None None 2023-11-07 08:25:43 UTC

Description Viktor Ashirov 2023-08-30 13:53:48 UTC 
Description of problem:
389-ds-base-2.3.6 contains fix https://github.com/389ds/389-ds-base/pull/5849
But it introduced a regression, I can no longer enable replication using consumer or hub role:

dsconf -v localhost replication enable --suffix=dc=example,dc=com --role=consumer --bind-dn="cn=replication manager,cn=config"
Error: Replica ID cannot be specified for consumer and hub roles

Version-Release number of selected component (if applicable):
389-ds-base-2.3.6-2.el9.x86_64

How reproducible:
always

Steps to Reproduce:
1. Create an instance
2. Enable replication using using consumer or hub role 


Actual results:
Error is displayed and replication is not enabled

Expected results:
Replication is enabled

Additional info:
Fix is a one-liner, see this discussion: https://github.com/389ds/389-ds-base/pull/5849/files#r1310241704
Comment 9 Viktor Ashirov 2023-09-13 09:47:17 UTC 
Automated test passed:
============================================================= test session starts =============================================================
platform linux -- Python 3.9.17, pytest-6.2.2, py-1.10.0, pluggy-0.13.1 -- /usr/bin/python3
cachedir: .pytest_cache
389-ds-base: 2.3.6-3.el9_3
nss: 3.90.0-3.el9_2
nspr: 4.35.0-3.el9_2
openldap: 2.6.3-1.el9
cyrus-sasl: 2.1.27-21.el9
FIPS: disabled
rootdir: /root/ds/dirsrvtests, configfile: pytest.ini
collected 9 items

dirsrvtests/tests/suites/clu/dsconf_test.py::test_backend_referral PASSED                                                               [ 11%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_dsconf_with_ldaps[ldapfile] PASSED                                                    [ 22%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_dsconf_with_ldaps[dsrfile] PASSED                                                     [ 33%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_check_replica_id_rejected_hub_consumer[consumer] PASSED                               [ 44%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_check_replica_id_rejected_hub_consumer[hub] PASSED                                    [ 55%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_check_replica_id_accepted_hub_consumer[consumer-None] PASSED                          [ 66%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_check_replica_id_accepted_hub_consumer[hub-None] PASSED                               [ 77%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_check_replica_id_accepted_hub_consumer[consumer-65535] PASSED                         [ 88%]
dirsrvtests/tests/suites/clu/dsconf_test.py::test_check_replica_id_accepted_hub_consumer[hub-65535] PASSED                              [100%]

================================================== 9 passed, 2 warnings in 170.40s (0:02:50) ==================================================

Marking as Verified:Tested.
Comment 12 bsmejkal 2023-09-13 12:25:27 UTC 
As per comment #c9 marking as VERIFIED.
Comment 14 errata-xmlrpc 2023-11-07 08:25:18 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-2023:6350
Note You need to log in before you can comment on or make changes to this bug.