Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1598662
Description of problem: When IPA server is installed on domain level-0 Replica installation fails with connection refused error Version-Release number of selected component (if applicable): Master- RHEL-6.10 ipa-server-3.0.0-51.el6.x86_64 Replica- RHEL-7.6 ipa-server-4.6.4-2.el7.x86_64 Steps to Reproduce: 1. Install Master on RHEL-6.10 2. Install replica on RHEL-7.6 Actual results: Replica installation fails Expected results: Replica installation should be successful Additional info: Previously replica installation was working on RHEL-7.5 using RHEL-6.9 as Master
Metadata Update from @frenaud: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1598662
Metadata Update from @tdudlak: - Issue assigned to tdudlak
I have tried using remote ports of ipa-3.0 master including: 9443 9444 9445 9446 using uri to rest api login and all attempts failed with 404.
Method dogtag.https_request() was running requests against replica's hostname. All requests and installation in the end finished successfuly when i used replica's hostname in step [23/27]: migrating certificate profiles to LDAP of configuring pki in dogtag.enter(self) method. I was struggling with finding a cause for it and Standa helped https://bugzilla.redhat.com/show_bug.cgi?id=1598662#c7
Metadata Update from @tdudlak: - Issue set to the milestone: FreeIPA 4.5.5 (was: FreeIPA 4.6.5)
Metadata Update from @tdudlak: - Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/2185
Metadata Update from @tdudlak: - Issue tagged with: regression
Ok this seems to confirm my suspicion that the ca_host change has these unexpected side-effects. Rather than talking to itself as a CA it is trying to talk to a remote server. Locally it was dogtag 10 so was trying to use the newer connection routines.
master:
ipa-4-6:
ipa-4-5:
ipa-4-7:
Metadata Update from @tdudlak: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)