Pulp 2 to Pulp 3 migration fails on RPM content that is not visible in Satellite
Environment
Red Hat Satellite 6.9
Issue
- running "Pulp 2 to Pulp 3 migration" script to prepare Sat6.9->6.10 upgrade
- the script fails with "Corrupted or missing content has been detected", listing some RPMs
- neither the RPM is visible in Satellite
Resolution
This should have been fixed in Satellite 6.9.6 via This content is not included.this bug being fixed there. In a rare case of unlucky timing, it still might be required to invoke pulp orphaned content removal manually:
foreman-rake katello:delete_orphaned_content
Wait until the pulp task on background succeeds: grep in /var/log/messages for delete_all_orphans and wait until you see the Task succeeded log as well, like:
Aug 20 16:14:13 pmoravec-sat69-on-rhev pulp: celery.worker.strategy:INFO: Received task: pulp.server.managers.content.orphan.delete_all_orphans[026508bc-9a14-4308-8f95-a750cdef9a03]
Aug 20 16:17:29 pmoravec-sat69-on-rhev pulp: celery.app.trace:INFO: [026508bc] Task pulp.server.managers.content.orphan.delete_all_orphans[026508bc-9a14-4308-8f95-a750cdef9a03] succeeded in 196.271635305s: {'erratum': 18, 'package_group': 308, 'package_category': 1, 'package_environment': 24, 'rpm': 378, 'yum_repo_metadata_file': 11}
Then re-run the migration again.
For more KB articles/solutions related to Red Hat Satellite 6.x Pulp 2.0 to Pulp 3.0 Migration Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Pulp 2.0 to Pulp 3.0 Migration Issues
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.