1600866 – katello-certs-check print "foreman-installer --scenario katello" and "foreman-proxy-certs-generate" on sat 6.4

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 1600866 - katello-certs-check print "foreman-installer --scenario katello" and "foreman-proxy-certs-generate" on sat 6.4

Summary: katello-certs-check print "foreman-installer --scenario katello" and "foreman...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Branding
Sub Component:
Version:	6.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	medium
Target Milestone:	6.4.0
Assignee:	satellite6-bugs
QA Contact:	Nikhil Kathole
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1625255
TreeView+	depends on / blocked

Reported:	2018-07-13 08:39 UTC by Nikhil Kathole
Modified:	2019-11-05 23:28 UTC (History)
CC List:	8 users (show)
Fixed In Version:	katello-installer-base-3.7.0.3-1
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2018-10-16 19:25:54 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Bugzilla	1627280	0	high	CLOSED	katello-certs-check output for capsule prints FOREMAN_PROXY	2021-02-22 00:41:40 UTC

Internal Links: 1627280

Description Nikhil Kathole 2018-07-13 08:39:10 UTC

Description of problem: Output of katello-certs-check utility prints

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

    foreman-installer --scenario katello\
                      --certs-server-cert "/tmp/server.valid.crt"\
                      --certs-server-key "/tmp/server.key"\
                      --certs-server-ca-cert "/tmp/rootCA.pem"

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

    foreman-installer --scenario katello\
                      --certs-server-cert "/tmp/server.valid.crt"\
                      --certs-server-key "/tmp/server.key"\
                      --certs-server-ca-cert "/tmp/rootCA.pem"\
                      --certs-update-server --certs-update-server-ca

To use them inside a NEW $FOREMAN_PROXY, run this command:

    foreman-proxy-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY"\
                                 --certs-tar  "~/$FOREMAN_PROXY-certs.tar"\
                                 --server-cert "/tmp/server.valid.crt"\
                                 --server-key "/tmp/server.key"\
                                 --server-ca-cert "/tmp/rootCA.pem"\

To use them inside an EXISTING $FOREMAN_PROXY, run this command INSTEAD:

    foreman-proxy-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY"\
                                 --certs-tar  "~/$FOREMAN_PROXY-certs.tar"\
                                 --server-cert "/tmp/server.valid.crt"\
                                 --server-key "/tmp/server.key"\
                                 --server-ca-cert "/tmp/rootCA.pem"\
                                 --certs-update-server


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

Satellite 6.4 snap 11


How reproducible: always


Steps to Reproduce:
1. katello-certs-check -c /tmp/server.valid.crt -k /tmp/server.key -b /tmp/rootCA.pem

Actual results: Output prints "foreman-installer --scenario katello" and "foreman-proxy-certs-generate".


Expected results: Output should print "satellite-installer --scenario satellite"
and "capsule-certs-generate"


Additional info:

Comment 3 Nikhil Kathole 2018-07-23 08:23:25 UTC

VERIFIED

Version tested:
satellite 6.4 snap 13

Validation succeeded.

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

    satellite-installer --scenario satellite\
                      --certs-server-cert "/tmp/server.valid.crt"\
                      --certs-server-key "/tmp/server.key"\
                      --certs-server-ca-cert "/tmp/rootCA.pem"

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

    satellite-installer --scenario satellite\
                      --certs-server-cert "/tmp/server.valid.crt"\
                      --certs-server-key "/tmp/server.key"\
                      --certs-server-ca-cert "/tmp/rootCA.pem"\
                      --certs-update-server --certs-update-server-ca

To use them inside a NEW $FOREMAN_PROXY, run this command:

    capsule-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY"\
                                 --certs-tar  "~/$FOREMAN_PROXY-certs.tar"\
                                 --server-cert "/tmp/server.valid.crt"\
                                 --server-key "/tmp/server.key"\
                                 --server-ca-cert "/tmp/rootCA.pem"\

To use them inside an EXISTING $FOREMAN_PROXY, run this command INSTEAD:

    capsule-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY"\
                                 --certs-tar  "~/$FOREMAN_PROXY-certs.tar"\
                                 --server-cert "/tmp/server.valid.crt"\
                                 --server-key "/tmp/server.key"\
                                 --server-ca-cert "/tmp/rootCA.pem"\
                                 --certs-update-server

Comment 9 Nikhil Kathole 2018-09-10 14:11:26 UTC

VERIFIED

Version tested:
sat 6.4 snap 21

if CN=$(hostname)

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 to see if the private key matches the certificate: 
[OK]

Checking CA bundle against the certificate file: 
[OK]

Checking Subject Alt Name on certificate 
[WARNING]

The /root/server.valid.crt does not contain a Subject Alt Name.
Checking Key Usage extension on certificate for Key Encipherment 
[OK]

Validation succeeded


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

    satellite-installer --scenario satellite\
                      --certs-server-cert "/root/server.valid.crt"\
                      --certs-server-key "/root/server.key"\
                      --certs-server-ca-cert "/root/rootCA.pem"

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

    satellite-installer --scenario satellite\
                      --certs-server-cert "/root/server.valid.crt"\
                      --certs-server-key "/root/server.key"\
                      --certs-server-ca-cert "/root/rootCA.pem"\
                      --certs-update-server --certs-update-server-ca

if CN!=$(hostname)

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 to see if the private key matches the certificate: 
[OK]

Checking CA bundle against the certificate file: 
[OK]

Checking Subject Alt Name on certificate 
[WARNING]

The /root/server.valid.crt does not contain a Subject Alt Name.
Checking Key Usage extension on certificate for Key Encipherment 
[OK]

Validation succeeded


  To use them inside a NEW $FOREMAN_PROXY, run this command:

      capsule-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY"\
                                   --certs-tar  "~/$FOREMAN_PROXY-certs.tar"\
                                   --server-cert "/root/server.valid.crt"\
                                   --server-key "/root/server.key"\
                                   --server-ca-cert "/root/rootCA.pem"\

  To use them inside an EXISTING $FOREMAN_PROXY, run this command INSTEAD:

      capsule-certs-generate --foreman-proxy-fqdn "$FOREMAN_PROXY"\
                                   --certs-tar  "~/$FOREMAN_PROXY-certs.tar"\
                                   --server-cert "/root/server.valid.crt"\
                                   --server-key "/root/server.key"\
                                   --server-ca-cert "/root/rootCA.pem"\
                                   --certs-update-server

Comment 12 Bryan Kearney 2018-10-16 19:25:54 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, 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-2018:2927

Note You need to log in before you can comment on or make changes to this bug.