Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2091995 - LEAPP upgrade fails without module_hotfixes=1
Summary: LEAPP upgrade fails without module_hotfixes=1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: sabuchan
QA Contact:
URL:
Whiteboard:
Depends On: 2089887
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-31 13:41 UTC by Brad Buckingham
Modified: 2023-02-07 13:38 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
*Leapp utility upgrade fails without `module_hotfixes=1`* If you do not run `module_hotfixes=1` before an in-place upgrade, the Leapp utility preupgrade check fails. To work around this for a Satellite Server, run `# subscription-manager repo-override --repo=satellite-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1` prior to the upgrade. To work around this for a Capsule Server, run `# subscription-manager repo-override --repo=satellite-capsule-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1` before the upgrade.
Clone Of: 2089887
Environment:
Last Closed: 2022-07-25 13:14:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-15706 0 None None None 2023-02-07 13:29:51 UTC
Red Hat Issue Tracker SATDOC-932 0 None None None 2022-05-31 13:46:16 UTC
Red Hat Knowledge Base (Solution) 6966647 0 None None None 2022-07-06 17:03:56 UTC

Comment 3 sabuchan 2022-06-14 19:08:48 UTC
RN initial draft doc is here: https://docs.google.com/document/d/1xMkjPbkwF9ZJ95tEcWYmRRqVdusIZENHZsL3-B3YvJw/edit

Tagged @bbuckingham to review.

RN draft:
The LEAPP preupgrade check fails if you do not run `module_hotfixes=1`. To work around this for Satellite, run `# subscription-manager repo-override --repo=satellite-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1` in your terminal, and for Satellite-Capsule, run `# subscription-manager repo-override --repo=satellite-capsule-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1` in your terminal.

Comment 4 Brad Buckingham 2022-06-15 13:30:44 UTC
ACK.  Minor update was provided on the doc.

Comment 5 sabuchan 2022-06-15 20:32:28 UTC
Final RN:

*Leapp utility upgrade fails without `module_hotfixes=1`*

If you do not run `module_hotfixes=1` before an in-place upgrade, the Leapp utility preupgrade check fails. 
To work around this for a Satellite Server, run `# subscription-manager repo-override --repo=satellite-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1` prior to the upgrade. 
To work around this for a Capsule Server, run `# subscription-manager repo-override --repo=satellite-capsule-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1` before the upgrade.


Note You need to log in before you can comment on or make changes to this bug.