Is it possible to ignore "WARNING" when migrating from pulp2 to pulp3?

Solution Unverified - Updated

Environment

Red Hat Satellite 6.9
Red Hat Satellite 6.10

Issue

Is it possible to ignore "WARNING" when migrating from pulp2 to pulp3?

# satellite-maintain content migration-stats
 Running Retrieve Pulp 2 to Pulp 3 migration statistics
 ================================================================================
 Retrieve Pulp 2 to Pulp 3 migration statistics: 
 ============Migration Summary================
 Migrated/Total RPMs: 163936/164936
 Migrated/Total errata: 356618/356618
 Migrated/Total repositories: 288/289
 Estimated migration time based on yum content: 0 hours, 15 minutes
 
 Note: ensure there is sufficient storage space for /var/lib/pulp/published to double in size before starting the migration process.
 Check the size of /var/lib/pulp/published with 'du -sh /var/lib/pulp/published/'
 
 Note: ensure there is sufficient storage space for postgresql.
 You will need additional space for your postgresql database.  The partition holding '/var/opt/rh/rh-postgresql12/lib/pgsql/data/'
    will need additional free space equivalent to the size of your Mongo db database (/var/lib/mongodb/).
 
 ============Missing/Corrupted Content Summary================
 WARNING: MISSING OR CORRUPTED CONTENT DETECTED
 Corrupted or Missing Rpm: 1000/164936
 Corrupted or missing content has been detected, you can examine the list of content in /tmp/unmigratable_content-*************** and take action by either:
 1. Performing a 'Verify Checksum' sync under Advanced Sync Options, let it complete, and re-running the migration
 2. Deleting/disabling the affected repositories and running orphan cleanup (foreman-rake katello:delete_orphaned_content) and re-running the migration
 3. Manually correcting files on the filesystem in /var/lib/pulp/content/ and re-running the migration
 4. Mark currently corrupted or missing content as skipped (foreman-rake katello:approve_corrupted_migration_content).  This will skip migration of missing or corrupted content.
                                                                       [OK]
 --------------------------------------------------------------------------------

Resolution

Warnings cannot be ignored because some data cannot be migrated.
Follow the steps to resolve the warning.

 ============Missing/Corrupted Content Summary================
 WARNING: MISSING OR CORRUPTED CONTENT DETECTED
 Corrupted or Missing Rpm: 1000/164936
 Corrupted or missing content has been detected, you can examine the list of content in /tmp/unmigratable_content-*************** and take action by either:
 1. Performing a 'Verify Checksum' sync under Advanced Sync Options, let it complete, and re-running the migration
 2. Deleting/disabling the affected repositories and running orphan cleanup (foreman-rake katello:delete_orphaned_content) and re-running the migration
 3. Manually correcting files on the filesystem in /var/lib/pulp/content/ and re-running the migration
 4. Mark currently corrupted or missing content as skipped (foreman-rake katello:approve_corrupted_migration_content).  This will skip migration of missing or corrupted content.

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

SBR
Product(s)
Components
Category

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.