Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
VERIFIED
Version Tested:
Satellite-6.3 Snap 25
steps:
1. Generated certs
2. Run Katello-certs-check with certs
# katello-certs-check -c server.valid.crt -k server.key -r server.csr -b rootCA.pem
Checking expiration of certificate: [OK]
Checking expiration of CA bundle: [OK]
Validating the certificate subject= /C=XX/L=Default City/O=Default Company Ltd
Checking to see if the private key matches the certificate: [OK]
Checking ca bundle against the cert file: [OK]
Checking for non ascii characters[OK]
Validation succeeded.
To install the Katello main server with the custom certificates, run:
foreman-installer --scenario katello\
--certs-server-cert "/root/certs/server.valid.crt"\
--certs-server-cert-req "/root/certs/server.csr"\
--certs-server-key "/root/certs/server.key"\
--certs-server-ca-cert "/root/certs/rootCA.pem"
To update the certificates on a currently running Katello installation, run:
foreman-installer --scenario katello\
--certs-server-cert "/root/certs/server.valid.crt"\
--certs-server-cert-req "/root/certs/server.csr"\
--certs-server-key "/root/certs/server.key"\
--certs-server-ca-cert "/root/certs/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 "/root/certs/server.valid.crt"\
--server-cert-req "/root/certs/server.csr"\
--server-key "/root/certs/server.key"\
--server-ca-cert "/root/certs/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 "/root/certs/server.valid.crt"\
--server-cert-req "/root/certs/server.csr"\
--server-key "/root/certs/server.key"\
--server-ca-cert "/root/certs/rootCA.pem"\
--certs-update-server
Successfully showed two different scenarios for NEW and EXISTING capsule to update certs.
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:0336
VERIFIED Version Tested: Satellite-6.3 Snap 25 steps: 1. Generated certs 2. Run Katello-certs-check with certs # katello-certs-check -c server.valid.crt -k server.key -r server.csr -b rootCA.pem Checking expiration of certificate: [OK] Checking expiration of CA bundle: [OK] Validating the certificate subject= /C=XX/L=Default City/O=Default Company Ltd Checking to see if the private key matches the certificate: [OK] Checking ca bundle against the cert file: [OK] Checking for non ascii characters[OK] Validation succeeded. To install the Katello main server with the custom certificates, run: foreman-installer --scenario katello\ --certs-server-cert "/root/certs/server.valid.crt"\ --certs-server-cert-req "/root/certs/server.csr"\ --certs-server-key "/root/certs/server.key"\ --certs-server-ca-cert "/root/certs/rootCA.pem" To update the certificates on a currently running Katello installation, run: foreman-installer --scenario katello\ --certs-server-cert "/root/certs/server.valid.crt"\ --certs-server-cert-req "/root/certs/server.csr"\ --certs-server-key "/root/certs/server.key"\ --certs-server-ca-cert "/root/certs/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 "/root/certs/server.valid.crt"\ --server-cert-req "/root/certs/server.csr"\ --server-key "/root/certs/server.key"\ --server-ca-cert "/root/certs/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 "/root/certs/server.valid.crt"\ --server-cert-req "/root/certs/server.csr"\ --server-key "/root/certs/server.key"\ --server-ca-cert "/root/certs/rootCA.pem"\ --certs-update-server Successfully showed two different scenarios for NEW and EXISTING capsule to update certs.