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.
Description of problem:
After you run the katello-certs-check cmd, you are given commands to run to the capsule-certs-generate command with all of its options (See bugs 1499323 and 1499316)
The output of the “capsule-certs-generate” command’s --capsule-certs-tar line, it does not provide the correct value for this option.
When you use the default certs from Satellite the “capsule-certs-generate” command’s --capsule-certs-tar line looks like:
> --capsule-certs-tar "~/mycapsule.mydomain.com-certs.tar"
But when you are using your own custom certs, that line looks like:
--capsule-certs-tar "~/-certs.tar"
Version-Release number of selected component (if applicable):
foreman-installer-katello-3.0.0.96-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Run katello-certs-check
2. Run capsule-certs-generate with custom certs
3.
Actual results:
Output like
--capsule-certs-tar "~/-certs.tar"
Expected results:
--capsule-certs-tar "~/mycapsule.mydomain.com-certs.tar"
Additional info:
Fixed upstream/6.3
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 "/etc/pki/katello/certs/katello-apache.crt"\
--server-cert-req "/etc/pki/katello/certs/katello-default-ca.crt"\
--server-key "/etc/pki/katello/private/katello-apache.key"\
--server-ca-cert "/etc/pki/katello/certs/katello-default-ca.crt"\
--certs-update-server
Description of problem: After you run the katello-certs-check cmd, you are given commands to run to the capsule-certs-generate command with all of its options (See bugs 1499323 and 1499316) The output of the “capsule-certs-generate” command’s --capsule-certs-tar line, it does not provide the correct value for this option. When you use the default certs from Satellite the “capsule-certs-generate” command’s --capsule-certs-tar line looks like: > --capsule-certs-tar "~/mycapsule.mydomain.com-certs.tar" But when you are using your own custom certs, that line looks like: --capsule-certs-tar "~/-certs.tar" Version-Release number of selected component (if applicable): foreman-installer-katello-3.0.0.96-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. Run katello-certs-check 2. Run capsule-certs-generate with custom certs 3. Actual results: Output like --capsule-certs-tar "~/-certs.tar" Expected results: --capsule-certs-tar "~/mycapsule.mydomain.com-certs.tar" Additional info: