Project

General

Profile

Actions

Bug #32663

closed

Pulp3 migration switchover fails when a content view contains two repositories with the same label

Added by Gerald Vogt over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Discussed here:

https://community.theforeman.org/t/contentmigration-switchover-fails-at-katello-pulp3-post-migration-check/23097/15

If a content view contains two repositories (of different products) with the same label, the resulting name for the pulp3 migration plan will be identical, causing to overwrite it and only one of the repositories being migrated. As the other isn't migrated and doesn't have a version_href, the switchover will fail even though the prepare before was successful.

The name for the migration plan is set here

https://github.com/Katello/katello/blob/9805b7a7ce90a3c10d74f29de4f75c261e203dfc/app/services/katello/pulp3/migration_plan.rb#L108

It doesn't contain the name of the product or any other unique identifier. However, if you add a repository to katello the label must only be unique for the specific product. If you have two products, e.g. foreman and foreman-client, both can have a repository with label "2_3_el7_x86_64". If both repositories are in the same content view, the migration plan will use the identical name for both repositories, causing an incomplete migration.

Actions

Also available in: Atom PDF