Bug 2164027

Summary:	[Documentation Bug] - Add steps to unset release version on Satellite server after leapp upgrade.
Product:	Red Hat Satellite	Reporter:	Dhaval Joshi <dhjoshi>
Component:	Documentation	Assignee:	Akshay Gadhave <agadhave>
Documentation sub component:	default	QA Contact:
Status:	MODIFIED ---	Docs Contact:
Severity:	high
Priority:	high	CC:	agadhave, egolov, risantam, saydas
Version:	6.11.4	Keywords:	Reopened, Triaged
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:	2023-02-09 04:43:21 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 Dhaval Joshi 2023-01-24 14:23:09 UTC

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/upgrading_and_updating_red_hat_satellite/index#upgrading-satellite-or-proxy-in-place-using-leapp_upgrade-guide 

Section Number and Name:
Chapter 4. Upgrading Satellite or Capsule to Red Hat Enterprise Linux 8 In-Place Using Leapp

Describe the issue: 
Under the Procedure section, after point # 10 and before point #11 add a new point that mentions unsetting the release version on the Satellite server and Capsule server.

Suggestions for improvement: 

Add the below commands and description:

Unset the release version on Red Hat Satellite and Capsule servers.

# subscription-manager release --unset
Release preference has been unset            <=== Expected Output

# subscription-manager release --show
Release not set                              <=== Expected Output

Additional information:
During the upgrade of RHEL OS from RHEL-7 to RHEL-8 using leapp utility, leapp sets release version 8.6 on the Satellite server. The customers facing issues with the upgrade of the Satellite server from 6.11 to 6.12 due to the release version 8.6. Hence, opening this documentation bug to add commands to unset the release version.

Comment 8 Eric Helms 2023-02-09 13:41:02 UTC

*** Bug 2163789 has been marked as a duplicate of this bug. ***

Comment 9 Sayan Das 2023-07-04 14:48:54 UTC

I am proposing to reopen the BZ. 

Earlier, What we did was to link https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/upgrading_from_rhel_7_to_rhel_8/performing-post-upgrade-tasks-rhel-7-to-rhel-8_upgrading-from-rhel-7-to-rhel-8 in our Satellite 6.11 upgrade guide and that RHEL doc used to contain the subscription-manager release --unset step.

After the release of RHEL 8.8, The "subscription-manager release --unset" step has been removed from the same RHEL doc\section and now after every leapp upgrade of a satellite\capsule, the sub-man release version is set to 8.8. It might not create any immediate issues right away but will become an issue when RHEL 8.9 or later versions will be released and someone would try to upgrade the satellite with the release version set to 8.8.

I still think we should execute "subscription-manager release --unset" via satellite-maintain only i.e. can perhaps be part of "repositories-setup" step of foreman-maintain. 

If that is not acceptable, then in https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/upgrading_and_updating_red_hat_satellite/upgrading-satellite-or-proxy-in-place-using-leapp_upgrade-guide , we need a 13th step to run "subscription-manager release --unset"

Comment 10 Evgeni Golov 2023-07-10 07:32:57 UTC

This (the `sub-man release --unset`) was hidden in the RHEL docs via https://gitlab.com/redhat/centos-stream/docs/enterprise-docs/-/commit/3774aae83fe0dbc4e8f64b394f80731f3be9ff63 -- it seems it gets enabled when there is an odd release and disabled when there is none (as right now 8.8 is the latest).

With that additional data, I tend to agree that we should re-open this BZ and explicitly add that step to our guide.

Comment 11 Sayan Das 2023-07-10 15:42:10 UTC

I am reopening this BZ based on Comment 9 and Comment 10. 

Feel free to reach out to me if any clarifications would be needed.