Bug 1498607

Summary: katello-backup does not backup custom certificates and need to ensure katello-restore restores them
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Backup & RestoreAssignee: Christine Fouant <cfouant>
Status: CLOSED ERRATA QA Contact: Corey Welton <cwelton>
Severity: high Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: bbuckingham, cdonnell, cwelton, ehelms
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
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:
: 1507981 (view as bug list) Environment:
Last Closed: 2018-02-21 17:00: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:
Bug Depends On:    
Bug Blocks: 1507981    

Description Mike McCune 2017-10-04 18:33:15 UTC
Satellite 6 servers using custom certificates do not have the source certificates stored in any standardized path, eg:

cat /etc/foreman-installer/scenarios.d/satellite-answers.yaml

... 

    server_cert: /root/certs/dogfood_server.crt
    server_key: /root/certs/dogfood_server.key
    server_cert_req: /root/certs/dogfood_server.csr
    server_ca_cert: /root/certs/ca.pem

we need to include these in every katello-backup we run so a server can be properly reconstituted.

Comment 3 Brad Buckingham 2017-10-10 11:48:21 UTC
Created redmine issue http://projects.theforeman.org/issues/21270 from this bug

Comment 4 Satellite Program 2017-10-17 08:24:32 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21270 has been resolved.

Comment 5 Corey Welton 2017-10-23 17:34:22 UTC
QE Verified that updated paths, when populated (e.g., custom certs), make it into the config files/archive saved by katello-backup

SNAP 21

Comment 6 Bryan Kearney 2018-02-21 17:00:44 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:0336