Project

Profile

Help

Issue #7092

closed

re-migration of errata that have now been copied to new repositories are not migrated for those new repositories

Added by jsherril@redhat.com over 3 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:

Description

If an errata is shared between two repositories it is migrated properly for both repos. If however you sync the errata into 1 repository, run the migration, copy the errata to another repository, and run the migration again, the errata isn't for the new repository.

Steps to reproduce:

  1. create a yum repo in pulp2, sync some repository with errata
  2. migrate the repository
  3. Create a 2nd yum repo in pulp2, copy the errata to it
  4. run the migration with both repositories

Results: the errata for the 2nd repository will not be migrated.

If you reset the pulp3 db and re-migrate, it all works fine and the errata are migrated for both repos.

This was tested with 0.2.0b5

Also available in: Atom PDF