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.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/upgrading_and_updating_red_hat_satellite/#migrating_satellite_server


Section Number and Name: 
2.2.4. Migrating a Satellite Server


Describe the issue: 
Apart of and similarly to carrying forward e.g. /var/lib/pulp, also /var/lib/qpidd needs to be copied. Otherwise pulp.agent.* queues wont be present after the migration and goferd / katello-agent on content hosts will fail to subscribe to these queues.


Suggestions for improvement: 
Please mention /var/lib/qpidd to copy.

Additional information:

Thank you for raising this bug.

These changes are now live on the customer portal:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#migrating_satellite_server

Thank you

The change is not ideal - in case customer migrated also pulp data (--skip-pulp-content option not used) "If you included Pulp data in the backup" point is to be followed and /var/lib/qpidd wont be copied.

Could the rsync command for qpidd be moved to a separate point, such that it is followed every time, regardless of "skipping" pulp content?

Hello Pavel,

Now we have to separate sub-procedure for those who "have less than 500 GB of Pulp data" and "have more than 500 GB of Pulp data".

The changes are now live on the customer portal. Please refer to the third step under Migrating a Satellite Server [1].

This was changed as a part of [2].

[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#migrating_satellite_server

[2] https://bugzilla.redhat.com/show_bug.cgi?id=1583169

Thank you