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:
It is a recommended way to don't use the default Administrator names. So I have changed this user. If I join a new computer to the IdM domain I specify this new name as "User authorized to enroll computers" and its password. The join works but always with an error message: "Unable to reliably detect configuration. Check NSS setup manually." and it will also call hardcode_ldap_server() which is not necessary because the test is wrong. So please use in /sbin/ipa-client-install line 2991 principal instead "admin@%s" if principal is set or find another way to test without hardcoded user names.
Version-Release number of selected component (if applicable):
ipa-client-4.2.0-15.el7_2.17.x86_64
Agreed, if a principal is provided for binding then that user should be used in the getent call.
This is just a sanity check to ensure that sssd is up and running and can identify users. The admin user is the only one created by IPA by default which is why it is currently hardcoded.
In any case this isn't considered a hard failure which is why the installation continues.