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: 'Unable to log in as uid=admin-replica.testrealm.test,ou=people,o=ipaca' during replica install
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Install IPA Server on RHEL7.9
2. Install IPA replica on RHEL8.8
3. Check the message displayed on the console.
Actual results:
2022-12-02T14:14:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG [3/30]: creating ACIs for admin
2022-12-02T14:14:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG [4/30]: creating installation admin user
2022-12-02T14:19:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG Unable to log in as uid=admin-replica.testrealm.test,ou=people,o=ipaca on ldap://master.testrealm.test:389
2022-12-02T14:19:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG [error] NotFound: uid=admin-replica.testrealm.test,ou=people,o=ipaca did not replicate to ldap://master.testrealm.test:389
2022-12-02T14:19:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG [hint] tune with replication_wait_timeout
2022-12-02T14:19:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG uid=admin-replica.testrealm.test,ou=people,o=ipaca did not replicate to ldap://master.testrealm.test:389
2022-12-02T14:19:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
2022-12-02T14:19:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG Your system may be partly configured.
2022-12-02T14:19:14+0000 [ipa_pytests.qe_class.QeHost.replica.cmd22] DEBUG Run /usr/sbin/ipa-server-install --uninstall to clean up.
Expected results:
ipa-replica-install should be successfull.
Additional info:
The replica installer creates a temporary user uid=admin-replica.testrealm.test,ou=people,o=ipaca on the 8.8 replica, that gets replicated to the 7.9 master. To ensure the user is properly replicated, the installer performs a bind on the master with the password.
The problem is that the user is created with a password encrypted using PBKDF2-SHA512, and if you try to do a ldap bind on the 7.9 master the op fails because this algo is not supported. As a consequence the replica installer assumes the user hasn't been replicated.
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 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:2811