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.

Created attachment 1408334 [details]
capsule cert tar file location is not consistent in the provided example commands

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

Steps to Reproduce:
1. On Satellite, run 'capsule-certs-generate'
2. See step 2 /root/capsule.example.com-certs.tar
3. See step 3 "/tmp/capsule.example.com-certs.tar"


Expected results:
The location should both be /root or /tmp.

Additional info:
See attached screenshot
Also, the error message should be more human readable if the user specifies the wrong location of the tar file. 

Thanks,
Julie

Created attachment 1453010 [details]
consistent location of capsule certs.tar in /root/

The capsule-certs-generate tar file is now displayed as located in the /root/ directory in the log output.

Verified in Satellite 6.4

*** Bug 1626106 has been marked as a duplicate of this bug. ***

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