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:
When you have a replica Setup, the replica is not making a copy of the ca to /usr/share/ipa/html/ca.crt, making ipa-client-install --Password= fail if a replica is hit, due to the Ca.crt missing.
ls -l /usr/share/ipa/html/ca.crt will come out empty
Where on Server 1 it will be there.
Check missing in replica install for ca.crt
And Client Needs to say if it can not download a ca.crt instead of giving wrong Password.
Version-Release number of selected component (if applicable):
ipa-client-common-4.4.0-12.el7.noarch
ipa-client-4.4.0-12.el7.x86_64
ipa-server-4.4.0-12.el7.x86_64
ipa-server-dns-4.4.0-12.el7.noarch
ipa-server-common-4.4.0-12.el7.noarch
ipa-server-trust-ad-4.4.0-12.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install IPA-server
2. Create Ad-Trust
3. setup-replica of IPA Server
4. Create Client ipa host-add hostname.example.com --Password=flaf
5. on Client ipa-client-install --Password=flaf
6. If IDM Server 1 is hit it will work, if replica is hit
Actual results:
Server Fails with Password wrong.
Expected results:
Server joined the AD.
Additional info: