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:
Getting the following warning message in syslog when migrating Pulp 2 contents to Pulp 3. This is because the downloaded flag of the rpm is 'true' but the file is actually missing in the file system.
------------------------------------------
pulpcore-worker-4: pulp: pulp_2to3_migration.app.plugin.content:WARNING: The content located in /var/lib/pulp/content/units/rpm/0b/15c68f607b781067527462f40cc725f5b8c9a8367553d85166f36566907d5f/abrt-dbus-2.1.11-60.el7.x86_64.rpm is missing or corrupted. It was skipped during Pulp 2to3 migration.
pulpcore-worker-4: pulp: pulp_2to3_migration.app.plugin.content:WARNING: The content located in /var/lib/pulp/content/units/rpm/9c/6735340ae17e9dbe28eafbd7cd48fdaa7b2b0bc1dfde64f2ec447298032e96/python-sss-murmur-1.16.5-10.el7.x86_64.rpm is missing or corrupted. It was skipped during Pulp 2to3 migration.
pulpcore-worker-4: pulp: pulp_2to3_migration.app.plugin.content:WARNING: The content located in /var/lib/pulp/content/units/rpm/b0/7e3260f44a48314acfca98d15e5e36f36c020e878b1eeceee269f4dc09bc3e/yum-plugin-versionlock-1.1.31-54.el7_8.noarch.rpm is missing or corrupted. It was skipped during Pulp 2to3 migration.
pulpcore-worker-4: pulp: pulp_2to3_migration.app.plugin.content:WARNING: The content located in /var/lib/pulp/content/units/rpm/9f/65006d676272c6203c9a245051dc6e4c88324d940d79f54695dcfb5b99538a/libxml2-devel-2.9.1-6.el7.5.x86_64.rpm is missing or corrupted. It was skipped during Pulp 2to3 migration.
pulpcore-worker-4: pulp: pulp_2to3_migration.app.plugin.content:WARNING: The content located in /var/lib/pulp/content/units/rpm/53/0e3905e55cc62766b57d01828be7df8add516a7ee42e4a2d6e6e6861dc6809/rdma-core-devel-22.4-5.el7.x86_64.rpm is missing or corrupted. It was skipped during Pulp 2to3 migration.
pulpcore-worker-4: pulp: pulp_2to3_migration.app.plugin.content:WARNING: The content located in /var/lib/pulp/content/units/rpm/c8/bc1538a67063c8404bb581ec1b40e5b0556d397006639b493d9c49f88b284a/dbus-1.10.24-15.el7.x86_64.rpm is missing or corrupted. It was skipped during Pulp 2to3 migration.
pulpcore-worker-4: pulp: pulp_2to3_migration.app.plugin.content:WARNING: The content located in /var/lib/pulp/content/units/rpm/eb/f474c54faa6d465bd18b6028836c25d517db165e59d1916a0a3f3a3ed3c187/kernel-headers-3.10.0-1160.el7.x86_64.rpm is missing or corrupted. It was skipped during Pulp 2to3 migration.
---------------------------------------------
Steps to Reproduce:
1. Remove one or more downloaded rpms files from the filesystem that are belonged to an on-demand repository.
2. Run the pulp 2 to pulp 3 migration script.
Actual results:
The rpm units are not migrated to Pulp 3
Expected results:
The rpm units should be migrated as long as they support on-demand and Pulp knows how to re-download them
As there is a patch available, it is possible to hotfix this if necessary, however as of yet it's late to add to 6.9 and there is no organic demand thus far.