Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 1858819 - katello-certs-check output print foreman-installer--scenario katello instead satellite-installer --scenario satellite
Summary: katello-certs-check output print foreman-installer--scenario katello instead...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.8.0
Assignee: Chris Roberts
QA Contact: Devendra Singh
URL:
Whiteboard:
: 1860085 1868028 1873399 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-20 13:30 UTC by Ganesh Payelkar
Modified: 2021-06-30 10:37 UTC (History)
7 users (show)

Fixed In Version: foreman-installer-2.1.2.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:04:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:04:41 UTC

Description Ganesh Payelkar 2020-07-20 13:30:55 UTC 
Description of problem:

katello-certs-check shows 'foreman-installer --scenario katello' instead of 

'satellite-installer --scenario satellite'


Version-Release number of selected component (if applicable):

satellite-6.8.0-0.7.beta.el7sat.noarch
foreman-installer-katello-2.1.0-1.el7sat.noarch

How reproducible:
New installation of 6.8 Beta

Steps to Reproduce:
1. Install new satellite 
2. Perform katello-certs-check with SSL certs
3.

Actual results: 

# katello-certs-check -c satellite-server.crt -k satellite_cert_key.pem -b ca.crt
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: 
[OK]

Checking Subject Alt Name on certificate 
[OK]

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

Validation succeeded


To install the Katello main server with the custom certificates, run:

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

To update the certificates on a currently running Katello installation, run:

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

To use them inside a NEW $FOREMAN_PROXY, rerun this command with -t foreman-proxy



Expected results: 

It must be "satellite-installer --scenario satellite" instead of "foreman-installer --scenario katello"


Additional info:
Comment 2 Chris Roberts 2020-08-10 13:59:49 UTC 
*** Bug 1860085 has been marked as a duplicate of this bug. ***
Comment 3 Brad Buckingham 2020-08-12 13:51:48 UTC 
*** Bug 1868028 has been marked as a duplicate of this bug. ***
Comment 5 Chris Roberts 2020-08-31 14:46:03 UTC 
*** Bug 1873399 has been marked as a duplicate of this bug. ***
Comment 6 Devendra Singh 2020-09-09 16:11:50 UTC 
Verified on 6.8 Snap14

Verification points:

1- Use git clone https://github.com/ekohl/ownca.git repository to create certificate

# ./ownca ca
Generating a 2048 bit RSA private key
.+++
.......................................+++
writing new private key to 'private/cakey.crt'
-----

# ./ownca cert xyz.com
Generating a 2048 bit RSA private key
................................................+++
...........................................................................................+++
writing new private key to './xyz.com/xyz.com.key'
-----
Using configuration from ./openssl.cnf
Check that the request matches the signature
Signature ok
The Subject's Distinguished Name is as follows
commonName            :PRINTABLE:'xyz.com'
Certificate is to be certified until Sep  9 15:54:21 2021 GMT (365 days)

Write out database with 1 new entries
Data Base Updated

# cp cacert.crt xyz.com/

# cd xyz.com

# openssl x509 -text -in xyz.com.crt -noout | grep -B1 DNS
X509v3 Subject Alternative Name: 
                DNS:xyz.com

# katello-certs-check -c xyz.com.crt -k xyz.com.key -b cacert.crt

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: 
[OK]

Checking Subject Alt Name on certificate 
[OK]

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

Validation succeeded


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

    satellite-installer --scenario satellite \
                      --certs-server-cert "/root/ownca/xyz.com/xyz.com.crt" \
                      --certs-server-key "/root/ownca/xyz.com/xyz.com.key" \
                      --certs-server-ca-cert "/root/ownca/xyz.com/cacert.crt"

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

    satellite-installer --scenario satellite \
                      --certs-server-cert "/root/ownca/xyz.com/xyz.com.crt" \
                      --certs-server-key "/root/ownca/xyz.com/xyz.com.key" \
                      --certs-server-ca-cert "/root/ownca/xyz.com/cacert.crt" \
                      --certs-update-server --certs-update-server-ca

To use them inside a NEW $CAPSULE, rerun this command with -t capsule
Comment 9 errata-xmlrpc 2020-10-27 13:04:20 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.8 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.