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.
Description of problem:
The official documentation here:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/html/upgrading_and_updating_red_hat_satellite/cloning_satellite_server#sec-Pulp_Data_Considerations
Advises that /var/lib/pulp can be omitted from the backup process and rsync'd to the target server independently.
We have rsync'd the /var/lib/pulp directory to the target server prior to running satellite-clone. When Satellite-clone is run the 800GB of pulp data that was rsync'd is wiped out by the process.
If there are additional steps required to utilize the rsync'd data they are either not present in the documentation for satellite-clone or not obvious.
Version-Release number of selected component (if applicable): 2.0.3-1
How reproducible:
Follow the documented instructions for satellite-clone
Steps to Reproduce:
1.Create a backup of the satellite using satellite-maintain backup and include the option --skip-pulp
2.Synchronize the contents of /var/lib/pulp from the source Satellite to the target server
3.Run satellite-cone
Actual results:
during the satellite-clone process the transferred contents of /var/lib/pulp are deleted.
Expected results:
The contents of /var/lib/pulp are recognized and used by the process
Additional info:
The deletion of the contents of /var/lib/pulp occurs during the execution of the task "restore using foreman-maintain" from /usr/share/satellite-clone/roles/satellite-clone/tasks/main.yml
If the option --skip-pulp is used <backup dir>/pulp_data.tar is not created. Both the satellite-clone role and foreman-maintain ruby gem seem to use the presence of pulp_data.tar as a flag.
This is impacting an active consulting engagement with a Red Hat customer.
Following the documentation as currently written leads one to use rsync to restore the Pulp filesystem BEFORE running the satellite-clone utility.
That procedure will never work, because satellite-clone uses `foreman-maintain restore ...` to import the data, and `foreman-maintain restore ...` first calls `satellite-installer --reset-data` which resets all databases and the Pulp filesystem (presumably this is done to import the data onto a "blank slate").
If rsyncing the Pulp filesystem is preferable for large deployments vs. collecting that data in the backup, it must be performed after `satellite-clone` has imported other data.
I'll change the component of this BZ to "documentation" for now. Please report back if the alternate ordering of the steps resolved the issue, and in that case it should be relatively straightforward to update the documentation with proper ordering of the steps. In case there is some other issue with the modified order, please report back for further evaluation.
Thank you,
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 19Red Hat Bugzilla
2024-10-05 04:25:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days