Bug 1291065 - Custom certificates not correctly deployed on capsule
Custom certificates not correctly deployed on capsule
Status: CLOSED DUPLICATE of bug 1218251
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Installer (Show other bugs)
6.1.3
Unspecified Linux
medium Severity medium (vote)
: Beta
: --
Assigned To: Katello Bug Bin
Kedar Bidarkar
: Triaged
Depends On: 1330566
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-13 06:59 EST by daniel
Modified: 2017-04-25 12:11 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-15 08:08:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description daniel 2015-12-13 06:59:17 EST
Description of problem:
When customer was following install guide to deploy custom certificates capsule was not working despite successful capsule-installer.
Customer found that
/etc/foreman-proxy/ssl_cert.pem
/etc/foreman-proxy/ssl_key.pem
have not been updated by the procedure and updated them manually, after that everything worked 

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


How reproducible:


Steps to Reproduce:
1. Set up Satellite and external Capsule and check it's working 
2. Apply custom certificates on Satellite6 following install guide
3. Apply custom certificate on Capsule following install guide and 
   output of capsule-certs-generate 

Actual results:
not all certificates on capsule got updated but
/etc/foreman-proxy/ssl_cert.pem
/etc/foreman-proxy/ssl_key.pem
had to be updated by hand

Expected results:
capsule-installer shall not show successful installation 


Additional info:
according to the log files i could not find any hints why this failed
Comment 6 Kedar Bidarkar 2016-05-02 07:18:36 EDT
I think the issue could be here with updating the capsule with the new certs.

I believe for some reason the new certs from the newer version of the created pacakges inside the tar file, do not get installed. 

Will check in more detail and update here.


NOTE: Setting up everything the first time itself using the custom certs, works completely fine.
Comment 7 Ivan Necas 2016-07-15 08:08:24 EDT
I think this is a duplicate of another bug that is actually ON_QE

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

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