Blame SOURCES/0007-Don-t-always-override-the-port-in-import_included_profiles_rhbz#2022483.patch

a47729
From edb216849e4f47d6cae95981edf0c3fe2653fd7a Mon Sep 17 00:00:00 2001
a47729
From: Rob Crittenden <rcritten@redhat.com>
a47729
Date: Fri, 28 Jan 2022 16:46:35 -0500
a47729
Subject: [PATCH] Don't always override the port in import_included_profiles
a47729
a47729
I can only guess to the original purpose of this override. I
a47729
believe it was because this is called in the installer prior
a47729
to Apache being set up. The expectation was that this would
a47729
only be called locally. It predates the RestClient class.
a47729
a47729
RestClient will attempt to find an available service. In this
a47729
case, during a CA installation, the local server is not
a47729
considered available because it lacks an entry in
a47729
cn=masters. So it will never be returned as an option.
a47729
a47729
So by overriding the port to 8443 the remote connection will
a47729
likely fail because we don't require that the port be open.
a47729
a47729
So instead, instantiate a RestClient and see what happens.
a47729
a47729
There are several use-cases:
a47729
a47729
1. Installing an initial server. The RestClient connection
a47729
   should fail, so we will fall back to the override port and
a47729
   use the local server. If Apache happens to be running with
a47729
   a globally-issued certificate then the RestClient will
a47729
   succeed. In this case if the connected host and the local
a47729
   hostname are the same, override in that case as well.
a47729
a47729
2. Installing as a replica. In this case the local server should
a47729
   be ignored in all cases and a remote CA will be picked with
a47729
   no override done.
a47729
a47729
3. Switching from CA-less to CA-ful. The web server will be
a47729
   trusted but the RestClient login will fail with a 404. Fall
a47729
   back to the override port in this case.
a47729
a47729
The motivation for this is trying to install an EL 8.x replica
a47729
against an EL 7.9 server. 8.5+ includes the ACME service and
a47729
a new profile is needed which doesn't exist in 7. This was
a47729
failing because the RestClient determined that the local server
a47729
wasn't running a CA so tried the remote one (7.9) on the override
a47729
port 8443. Since this port isn't open: failure.
a47729
a47729
Chances are that adding the profile is still going to fail
a47729
because again, 7.9 lacks ACME capabilities, but it will fail in
a47729
a way that allows the installation to continue.
a47729
a47729
I suspect that all of the overrides can similarly handled, or
a47729
handled directly within the RestClient class, but for the sake
a47729
of "do no harm" I'm only changing this instance for now.
a47729
a47729
https://pagure.io/freeipa/issue/9100
a47729
a47729
Signed-off-by: Rob Crittenden <rcritten@redhat.com>
a47729
Reviewed-By: Florence Blanc-Renaud <frenaud@redhat.com>
a47729
---
a47729
 ipaserver/install/cainstance.py | 30 +++++++++++++++++++++++++++++-
a47729
 1 file changed, 29 insertions(+), 1 deletion(-)
a47729
a47729
diff --git a/ipaserver/install/cainstance.py b/ipaserver/install/cainstance.py
a47729
index 8c8bf1b3a..ad206aad4 100644
a47729
--- a/ipaserver/install/cainstance.py
a47729
+++ b/ipaserver/install/cainstance.py
a47729
@@ -1953,7 +1953,35 @@ def import_included_profiles():
a47729
         cn=['certprofiles'],
a47729
     )
a47729
 
a47729
-    api.Backend.ra_certprofile.override_port = 8443
a47729
+    # At this point Apache may or may not be running with a valid
a47729
+    # certificate. The local server is not yet recognized as a full
a47729
+    # CA yet so it isn't discoverable. So try to do some detection
a47729
+    # on what port to use, 443 (remote) or 8443 (local) for importing
a47729
+    # the profiles.
a47729
+    #
a47729
+    # api.Backend.ra_certprofile invokes the RestClient class
a47729
+    # which will discover and login to the CA REST API. We can
a47729
+    # use this information to detect where to import the profiles.
a47729
+    #
a47729
+    # If the login is successful (e.g. doesn't raise an exception)
a47729
+    # and it returns our hostname (it prefers the local host) then
a47729
+    # we override and talk locally.
a47729
+    #
a47729
+    # Otherwise a NetworkError means we can't connect on 443 (perhaps
a47729
+    # a firewall) or we get an HTTP error (valid TLS certificate on
a47729
+    # Apache but no CA, login fails with 404) so we override to the
a47729
+    # local server.
a47729
+    #
a47729
+    # When override port was always set to 8443 the RestClient could
a47729
+    # pick a remote server and since 8443 isn't in our firewall profile
a47729
+    # setting up a new server would fail.
a47729
+    try:
a47729
+        with api.Backend.ra_certprofile as profile_api:
a47729
+            if profile_api.ca_host == api.env.host:
a47729
+                api.Backend.ra_certprofile.override_port = 8443
a47729
+    except (errors.NetworkError, errors.RemoteRetrieveError) as e:
a47729
+        logger.debug('Overriding CA port: %s', e)
a47729
+        api.Backend.ra_certprofile.override_port = 8443
a47729
 
a47729
     for (profile_id, desc, store_issued) in dogtag.INCLUDED_PROFILES:
a47729
         dn = DN(('cn', profile_id),
a47729
-- 
a47729
2.34.1
a47729