Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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