Project

General

Profile

Actions

Bug #15184

closed

Upgrade fails when there is content and a capsule

Added by Brad Buckingham almost 8 years ago. Updated almost 6 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1339682
Description of problem:

The Satellite upgrade fails when there is a capsule installed and a repo synced.

/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]

Version-Release number of selected component (if applicable):

6.1 > 6.2 upgrade

How reproducible:

Always

Steps to Reproduce:
1. Install Satellite 6.1
2. Install a capsule
3. Sync a repo
4. Upgrade to 6.2

Actual results:

Upgrade fails

Expected results:

upgrade succeeds

Additional info:
I had one zoo repo synced to the Satellite.

I also attached an excerpt from the log where I believe the issue is, it looks like the migration fails, which makes it so there is pending migrations on the seeds step.
Actions #1

Updated by The Foreman Bot almost 8 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Brad Buckingham
  • Pull request https://github.com/Katello/katello/pull/6066 added
Actions #2

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release set to 86
Actions #3

Updated by Brad Buckingham almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF