Description of problem: Output of katello-certs-check output shows 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/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: foreman-proxy-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 To install the Katello main server with the custom certificates, run: foreman-installer --scenario katello\ --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: foreman-installer --scenario katello\ --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 Version-Release number of selected component (if applicable): Satellite 6.5.0 snap 1 How reproducible: always Steps to Reproduce: 1. katello-certs-check -c server.valid.crt -k server.key -b rootCA.pem Actual results: Output showed foreman-installer/foreman-proxy-certs-generate/Katello/foreman-proxy words. Expected results: Replace : s/foreman-installer/satellite-installer s/foreman-proxy-certs-generate/capsule-certs-generate s/foreman-proxy/capsule s/katello/satellite Additional info:
VERIFIED Version tested: Satellite 6.5 snap 4 To install the Satellite 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 Satellite 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 To use them inside a NEW $CAPSULE, run this command: capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" \ --certs-tar "~/$CAPSULE-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 $CAPSULE, run this command INSTEAD: capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" \ --certs-tar "~/$CAPSULE-certs.tar" \ --server-cert "/root/server.valid.crt" \ --server-key "/root/server.key" \ --server-ca-cert "/root/rootCA.pem" \ --certs-update-server
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-2019:1222