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 2103920 - Missing steps from "Upgrading Satellite from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8" section of Satellite 6.11 upgrade guide
Summary: Missing steps from "Upgrading Satellite from Red Hat Enterprise Linux 7 to Re...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Brian Angelica
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-05 09:46 UTC by Sayan Das
Modified: 2022-07-22 19:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-22 19:06:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SATDOC-977 0 None None None 2022-07-05 09:49:13 UTC

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


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