Bug #34045
closedExecuting remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories.
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2025049 \n\n*Description of problem:*\nExecuting remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories. Keeping the pulp2 content will not break Red Hat repos and synchronizations.\n\n*Version-Release number of selected component (if applicable):*\n6.10.1\n\n*How reproducible:*\nEvery time.\n\n*Steps to Reproduce:*\n1.After completing the satellite 6.10 upgrade run remove-pulp2 to cleanup content\n2.Sync repos\n3.Sync fails \n\n\n*Actual results:*\nRepos sync with warning:\nrelation "pulp_2to3_migration_pulp2repository" does not exist\nLINE 1: ...ation_pulp2repository"."pulp3_repository_id" FROM "pulp_2to3...\n\n*Expected results:*\nRepos should synchronize correctly\n\n*Additional info:*
Updated by James Jeffers about 3 years ago
- Project changed from Katello to Foreman Maintain
- Subject changed from Executing remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories. to Executing remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories.
- Target version deleted (
Katello 4.4.0)
Updated by The Foreman Bot about 3 years ago
- Status changed from New to Ready For Testing
- Assignee set to James Jeffers
- Pull request https://github.com/theforeman/foreman_maintain/pull/570 added
Updated by James Jeffers about 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_maintain|35b8b63793a0a7091f73d87c657a4a7ea63f7c21.