Project

General

Profile

Actions

Bug #34045

closed

Executing remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories.

Added by James Jeffers over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

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:*

Actions #1

Updated by James Jeffers over 2 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)
Actions #2

Updated by The Foreman Bot over 2 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
Actions #3

Updated by James Jeffers over 2 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF