Bug 1507981
Summary: | katello-backup does not backup custom certificates and need to ensure katello-restore restores them | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Brad Buckingham <bbuckingham> |
Component: | Backup & Restore | Assignee: | Christine Fouant <cfouant> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | Unspecified | CC: | bbuckingham, cdonnell, cfouant, cwelton, ehelms, mmccune, sthirugn |
Target Milestone: | Unspecified | Keywords: | 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: | 1498607 | Environment: | |
Last Closed: | 2017-11-20 16:42:23 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: | 1498607 | ||
Bug Blocks: |
Comment 2
Satellite Program
2017-10-31 16:18:02 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21270 has been resolved. Verified in 6.2.12 Async. I followed roughly the same steps as Suresh outlined in Comment #7. 1. Installed Satellite without custom certs. 2. Performed basic actions (content) to establish backup content. 3. Installed custom certs 4. Verified basic actions still worked. 5. Performed a backup. 6. Verified that the custom certs were not backed up. 7. Installed the packages being delivered in this async. 8. Performed another backup. Result: The certs were included in config_files.tar.gz, preserving their original file structure 9. I then copied the backup files to a new server 10. Used satellite-clone to install satellite and restore the backup. Result: The clone completed successfully, restoring the certificate's file structure and using the same answers file from the original Satellite. 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/RHBA-2017:3251 |