Bug 1556703

Summary: Inconsistent examples in capsule-certs-generate screen output
Product: Red Hat Satellite Reporter: Julie <juwu>
Component: InstallationAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Chris Brown <dbrownjr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: chrobert, ddolguik, jhutar, jjansky
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: https://projects.theforeman.org/issues/22949
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 18:55:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
capsule cert tar file location is not consistent in the provided example commands
none
consistent location of capsule certs.tar in /root/ none

Description Julie 2018-03-15 05:53:37 UTC
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

Comment 2 Chris Brown 2018-06-19 18:38:56 UTC
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.

Comment 3 Chris Brown 2018-06-19 18:45:59 UTC
Verified in Satellite 6.4

Comment 5 Eric Helms 2018-09-11 15:13:30 UTC
*** Bug 1626106 has been marked as a duplicate of this bug. ***

Comment 6 Bryan Kearney 2018-10-16 18:55:19 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