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.

Bug 1461782

Summary: [RFE] Make katello-certs-check return absolute paths
Product: Red Hat Satellite Reporter: Tapomoy Bhowmik <tbhowmik>
Component: OtherAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.9CC: calba, inecas, jcallaha
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-20 19:38:44 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:

Description Tapomoy Bhowmik 2017-06-15 10:23:21 UTC
Description of problem: The katello-certs-check returns the command for possible operations with satellite-installer after verifying the provided files are correct.

Problem is if the parameters are relative to the position of the execution, say 

-----------
# katello-certs-check -c  xxx.example.com.cer -r xxx.example.com.csr -k  xxx.example.com.key -b  /etc/pki/ca-trust/source/anchors/ISSUECATID_bundle_2016-2030.cer
----------

It returns the satellite-installer command with the same relative paths which, as the installer passed the parameters verbatim to the satellite-answers file, breaks a number of things.

-----------------
..............
To install the Satellite main server with the custom certificates, run:

    satellite-installer --scenario satellite\
                        --certs-server-cert "xxx.example.com.cer"\
                        --certs-server-cert-req "xxx.example.com.csr"\
                        --certs-server-key "xxx.example.com.key"\
                        --certs-server-ca-cert "/etc/pki/ca-trust/source/anchors/ISSUECATID_bundle_2016-2030.cer"
...............
------------------

Proposed change is to katello-certs-check to calculate the real path of the files and add them to the satellite-installer commands so the admin doesn't hit a problem later.


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


How reproducible: N/A


Steps to Reproduce: N/A


Actual results: It returns the satellite-installer command with the same relative paths which, as the installer passed the parameters verbatim to the satellite-answers file, breaks a number of things.


Expected results: katello-certs-check to calculate the real path of the files and add them to the satellite-installer commands so the admin doesn't hit a problem later.


Additional info:

Comment 1 jcallaha 2017-06-20 19:38:44 UTC
This is a duplicate and fixed in 6.3.

*** This bug has been marked as a duplicate of bug 1358935 ***