Bug 1873399

Summary: katello-certs-check does not have "satellite" or "capsule" to be selected as valid target types.
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Devendra Singh <desingh>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: chrobert
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-31 14:46:03 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 Sayan Das 2020-08-28 07:23:47 UTC 
Description of problem:

katello-certs-check does not have "satellite" or "capsule" to be selected as valid target types. Only applicable options are "-t foreman" or "-t foreman-proxy".


Version-Release number of selected component (if applicable):
satellite-6.8.0-0.7.beta.el7sat.noarch
foreman-installer-katello-2.1.1-2.el7sat.noarch

How reproducible:
Always


Steps to Reproduce:
1. Execute "katello-certs-check -h" on satellite server.


Actual results:
# katello-certs-check -h
/usr/sbin/katello-certs-check: illegal option -- h
Verifies, that custom SSL certificate files are usable
as part of the Katello installation. When passing filenames use absolute paths.

usage: /usr/sbin/katello-certs-check -t [foreman|foreman-proxy] -c CERT_FILE -k KEY_FILE -b CA_BUNDLE_FILE



Expected results:
# katello-certs-check -h
/usr/sbin/katello-certs-check: illegal option -- h
Verifies, that custom SSL certificate files are usable
as part of the Red Hat Satellite installation. When passing filenames use absolute paths.

usage: /usr/sbin/katello-certs-check -t [satellite|capsule] -c CERT_FILE -k KEY_FILE -b CA_BUNDLE_FILE



Additional info:
NA
Comment 2 Chris Roberts 2020-08-31 14:46:03 UTC 

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