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 1508621 - hammer SSL errors when using custom certificates on Satellite server
Summary: hammer SSL errors when using custom certificates on Satellite server
Keywords:
Status: CLOSED DUPLICATE of bug 1501980
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-01 19:24 UTC by Eric Helms
Modified: 2019-04-01 20:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-08 15:07:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eric Helms 2017-11-01 19:24:33 UTC
Description of problem:
On a default install of 6.3, when using custom certificates, hammer will throw an SSL error due to being configured to use the wrong SSL CA certificate.

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


How reproducible:


Steps to Reproduce:
1. Install 6.3 with custom certificates
2. Run 'hammer organization list'
3.

Actual results:
Could not load the API description from the server: SSL certificate verification failed

Expected results:
Hammer lists organizations

Additional info:

This breaks due to /etc/hammer/cli.modules.d/foreman.yml being configured to have ssl_ca_file pointed at /etc/pki/katello/certs/katello-default-ca.crt. This certificate is not the CA being used by the Foreman webserver when custom certificates are being used. Rather, this should be configured to point at:

/etc/pki/katello/certs/katello-server-ca.crt

This comes from the fact that puppet-foreman cli modules (in the installer as foreman::cli) configures the ssl_ca_file based on the server_ssl_ca parameter from the main Foreman configuration [1]. This should either be explicitly configured in the installer or the logic updated here to grab the server_ssl_chain.


[1] https://github.com/theforeman/puppet-foreman/blob/master/manifests/cli.pp#L47

Comment 2 Brad Buckingham 2017-11-08 15:07:29 UTC
This appears to be a duplicate of bug 1501980

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


Note You need to log in before you can comment on or make changes to this bug.