Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The 1.4.3.29-3 has a regression where it is impossible to create a winsync replication agreement as it fails with:
Error: 105 - 5 - 53 - Server is unwilling to perform - []
and in the errors log:
ERR - NSMMReplicationPlugin - agmt_new_from_entry: failed to initialise windows replicationagreement "agmt="cn=WinsyncToMSAD" (msad:389)" - replica is not a supplier (may be hub or consumer).
The instance is configured as supplier and the changelog is enabled.
This problem is neither present in 1.4.3.28-7 nor the upstream so this is a regression introduced somewhere between 1.4.3.28-7 and 1.4.3.29-3.
Version-Release number of selected component (if applicable):
1.4.3.29-3
How reproducible:
always
Steps to Reproduce:
1. update to 1.4.3.29-3
2. dscreate an instance
3. enable replication
4. dsconf -D "cn=Directory Manager" ldap://localhost:1389 repl-winsync-agmt create --suffix="dc=test" --host="msad.example389.com" --port=389 --conn-protocol="LDAP" --bind-dn="cn=Administrator,cn=Users,DC=EXAMPLE389,DC=COM" --bind-passwd="password" --win-subtree="CN=Users,DC=EXAMPLE389,DC=COM" --ds-subtree="dc=test" --win-domain="EXAMPLE389.COM" --init WinsyncToMSAD
Actual results:
Error: 105 - 5 - 53 - Server is unwilling to perform - []
Expected results:
Winsync replication agreement creation should succeed.
Additional info:
My guess is that some repl init code has either been shuffled or broken in this case as agmt_new_from_entry() conditions for nsDSWindowsReplicationAgreement check fail for no apparent reason tho i did not have time to debug it.