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.
DescriptionJustin Sherrill
2021-03-25 19:11:08 UTC
Steps:
1) sync a repo with at least one errata
2) migrate the content (foreman-maintain content prepare)
3) reset the migration (foreman-maintain content migration-reset)
4) remigrate (foreman-maintain content prepare)
5) check un-migrated errata:
Katello::RepositoryErratum.where(erratum_pulp3_href: nil).count
This should be zero, but ends up being all RepositoryErratum entries.
The cause of this is this line:
<pre>
last_migration_time = last_successful_migration_time
offset = 0
limit = SETTINGS[:katello][:pulp][:bulk_load_size]
response = pulp2_content_api.list(pulp2_content_type_id: 'erratum', offset: offset, limit: limit, pulp2_last_updated__gt: last_migration_time)
</pre>
last_successful_migration_time doesn't seem to take into account a reset action (where everything needs to be re-imported)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Satellite 6.9.1 Async Bug Fix Update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:1371
Steps: 1) sync a repo with at least one errata 2) migrate the content (foreman-maintain content prepare) 3) reset the migration (foreman-maintain content migration-reset) 4) remigrate (foreman-maintain content prepare) 5) check un-migrated errata: Katello::RepositoryErratum.where(erratum_pulp3_href: nil).count This should be zero, but ends up being all RepositoryErratum entries. The cause of this is this line: <pre> last_migration_time = last_successful_migration_time offset = 0 limit = SETTINGS[:katello][:pulp][:bulk_load_size] response = pulp2_content_api.list(pulp2_content_type_id: 'erratum', offset: offset, limit: limit, pulp2_last_updated__gt: last_migration_time) </pre> last_successful_migration_time doesn't seem to take into account a reset action (where everything needs to be re-imported)