Bug 2254085

Summary: Getting '/usr/sbin/foreman-rake db:migrate' returned 1 instead of one of [0] ERROR while trying to upgrade Satellite 6.13 to 6.14
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: Hosts - ContentAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: Sam Bible <sbible>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 6.14.0CC: ahumbe, ehelms, jentrena, jlenz, lvrtelov, pdwyer, rlavi, sbible
Target Milestone: 6.14.1Keywords: EasyFix, Triaged, Upgrades
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.18-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2252064 Environment:
Last Closed: 2023-12-14 16:26:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 4 Sam Bible 2023-12-13 18:58:36 UTC
Verified on 6.14.1 - Snap 2.1

Steps to Verify:
1. Spin up a 6.13 Satellite.
2. Create a Content View and promote to Library.
3. Create a new LCE, and make sure that it doesn't contain the CV
4. Create a Host, and through using some katello-rake commands from https://github.com/Katello/katello/pull/10817, assign it the Content View, and the LCE that doesn't contain the CV.
5. Attempt to upgrade to 6.14.1

Expected Results:
You don't run into any issues during the DB Migration step, and the upgrade completes successfully.

Actual Results:
You don't run into any issues during the DB Migration step, and the upgrade completes successfully.

Comment 8 errata-xmlrpc 2023-12-14 16:26:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.14.1 Async Security Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:7851