Project

General

Profile

Actions
Copy link

Bug #32888

closed

Promoting a content view or publishing/promoting a composite after initial migration causes errata to never be migrated

Added by Justin Sherrill over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Justin Sherrill
Category:
Repositories
Target version:
Katello 3.18.4
Difficulty:
Triaged:
Yes
Bugzilla link:
1976351
Pull request:
https://github.com/Katello/katello/pull/9431
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1976351

Steps to Reproduce:
1. Create and sync some repo with errata
2. Publish the repo in a content view
3. run 'foreman-maintain content prepare'
4. Note in 'foreman-maintain content migration-stats' that all errata are migrated

Next do one of the following:

5. promote the CV to a new lifecycle environment
OR
5. publish the CV in a composite content view

6. Re-run the migration 'foreman-maintain content prepare'
7. Re-run 'foreman-maintain content migration-stats'

Actual results:

Not all errata will be migrated, error given when running switchover

Expected results:
All errata are migrated

Additional info:

Actions
Copy link
 #1

Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Justin Sherrill
  • Pull request https://github.com/Katello/katello/pull/9431 added
Actions
Copy link
 #2

Updated by Chris Roberts over 3 years ago

  • Target version set to Katello 3.18.4
  • Triaged changed from No to Yes
Actions
Copy link
 #3

Updated by Jonathon Turel over 3 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF