Actions
Bug #15184
closedUpgrade fails when there is content and a capsule
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