Bug 2103920

Summary: Missing steps from "Upgrading Satellite from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8" section of Satellite 6.11 upgrade guide
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: DocumentationAssignee: Brian Angelica <bangelic>
Documentation sub component: default QA Contact:
Status: CLOSED WORKSFORME Docs Contact:
Severity: high    
Priority: high CC: bangelic, egolov, mdolezel
Version: 6.11.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-22 19:06:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sayan Das 2022-07-05 09:46:13 UTC
Document URL: 

NA at this moment ( Satellite 6.11 Upgrade guide ) ( both connected and disconnected )

Section Number and Name: 

3.6. Upgrading Satellite from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8

Describe the issue and Suggestions for improvement: 

There are two problems present.

A) We are mentioning this in the Release notes of Satellite 6.11:

~~~~~~~~~~~~~~~~~~~~~~~~~
Leapp utility does not properly enable the Satellite module

The Leapp utility does not properly enable the Satellite module.

To work around this issue, run the following commands prior to the upgrade:


# subscription-manager repo-override --repo=satellite-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1 (for {Project} Server)


# subscription-manager repo-override --repo=satellite-capsule-6.11-for-rhel-8-x86_64-rpms --add=module_hotfixes:1(for  {SmartProxyServer})

BZ#(2091995)
~~~~~~~~~~~~~~~~~~~~~~~~~~

But since this is something the users will have to perform everytime they try leapp, This info should be part of  "3.6. Upgrading Satellite from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8" as well.

If not entire solution, Then atleast a link to Release Notes to check "Leapp utility does not properly enable the Satellite module" point is what should be present.



B) In my recent testing on GA snap, The After completeing the leapp upgrade i.e. after Step 8, Users will need to:

** Complete the post-upgrade steps as per https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/upgrading_from_rhel_7_to_rhel_8/index#verifying-the-post-upgrade-state-of-the-rhel-8-system_upgrading-from-rhel-7-to-rhel-8 

    --> This may seem something expected but A link to the post-upgrade doc of leapp, completes for the entire workflow of leapp in Sat doc. 

** If they expect selinux to be in enforcing mode, Then apart from doing the steps from https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/upgrading_from_rhel_7_to_rhel_8/index#changing-selinux-mode-to-enforcing_applying-security-policies, Additionally they will need to perform the following steps on Satellite .

# foreman-maintain service stop
# dnf reinstall foreman-selinux katello-selinux --disableplugin=foreman-protector
# foreman-maintain service start
# sleep 20 && hammer ping

( Nothing needed for capsules )



Additional information: 


Check private notes