Bug 2073305

Summary: installer spams with katello-certs-check output when using custom certs
Product: Red Hat Satellite Reporter: Evgeni Golov <egolov>
Component: InstallationAssignee: Eric Helms <ehelms>
Status: CLOSED ERRATA QA Contact: Omkar Khatavkar <okhatavk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: ahumbe, ehelms, zhunting
Target Milestone: 6.12.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-16 13:33:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Evgeni Golov 2022-04-08 07:51:02 UTC
Description of problem:
When using custom certs, and running the installer to enable a feature or anything, it re-runs katello-certs-check to verify certs and the output is visible on the shell, confusing the user:

 foreman-installer 
2022-04-08 07:46:31 [NOTICE] [root] Loading installer configuration. This will take some time.
2022-04-08 07:46:38 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2022-04-08 07:46:38 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
Package versions are locked. Continuing with unlock.
Executing: katello-certs-check -c "/root/satellite_cert/satellite_cert.pem" -k "/root/satellite_cert/satellite_cert_key.pem" -b "/root/satellite_cert/ca_cert_bundle.pem"
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Checking server certificate encoding: [OK]

Checking expiration of certificate: [OK]

Checking expiration of CA bundle: [OK]

Checking if server certificate has CA:TRUE flag [OK]

Checking for private key passphrase: [OK]

Checking to see if the private key matches the certificate: [OK]

Checking CA bundle against the certificate file: [OK]

Checking CA bundle size: 3
[OK]

Checking Subject Alt Name on certificate [OK]

Checking if any Subject Alt Name on certificate matches the Subject CN
[OK]

Checking Key Usage extension on certificate for Key Encipherment [OK]

Checking for use of shortname as CN
[OK]

Validation succeeded


To install the Red Hat Satellite server with the custom certificates, run:

    satellite-installer --scenario satellite \
                      --certs-server-cert "/root/satellite_cert/satellite_cert.pem" \
                      --certs-server-key "/root/satellite_cert/satellite_cert_key.pem" \
                      --certs-server-ca-cert "/root/satellite_cert/ca_cert_bundle.pem"

To update the certificates on a currently running Red Hat Satellite installation, run:

    satellite-installer --scenario satellite \
                      --certs-server-cert "/root/satellite_cert/satellite_cert.pem" \
                      --certs-server-key "/root/satellite_cert/satellite_cert_key.pem" \
                      --certs-server-ca-cert "/root/satellite_cert/ca_cert_bundle.pem" \
                      --certs-update-server --certs-update-server-ca

To use them inside a NEW $CAPSULE, rerun this command with -t capsule
2022-04-08 07:46:53 [NOTICE] [configure] Starting system configuration.
…

Version-Release number of selected component (if applicable):
foreman-installer-3.1.2.1-1.el8sat.noarch
foreman-installer-katello-3.1.2.1-1.el8sat.noarch
satellite-installer-6.11.0.5-1.el8sat.noarch


How reproducible:
100%

Steps to Reproduce:
1. install with certs
2. call installer again

Actual results:
certs-check output as above

Expected results:
silence

Additional info:

Comment 3 Eric Helms 2022-05-10 15:10:40 UTC
Created redmine issue https://projects.theforeman.org/issues/34888 from this bug

Comment 4 Bryan Kearney 2022-05-11 00:04:54 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34888 has been resolved.

Comment 10 errata-xmlrpc 2022-11-16 13:33:46 UTC
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 (Important: Satellite 6.12 Release), 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/RHSA-2022:8506