Project

General

Profile

Bug #32210

Pulp3 Migration after migration reset doesn't import errata info from pulp3

Added by Justin Sherrill about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

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:

        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)

last_successful_migration_time doesn't seem to take into account a reset action (where everything needs to be re-imported)

History

#1 Updated by Justin Sherrill about 2 years ago

  • Bugzilla link set to 1943317

#2 Updated by The Foreman Bot about 2 years ago

  • Assignee set to Justin Sherrill
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/9244 added

#3 Updated by Justin Sherrill about 2 years ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.18.3

#4 Updated by Justin Sherrill about 2 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF