Bug 2143365

Summary:	[RFE] satellite-maintain doesn't deal with unsetting RHEL version or upgrading RPMs to "current"
Product:	Red Hat Satellite	Reporter:	Ben <ben.argyle>
Component:	Leapp integration	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.12.0	CC:	ahumbe, aruzicka, lstejska, rlavi
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
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:		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 Ben 2022-11-16 18:10:47 UTC

Description of problem:
When LEAPPing a RHEL 7 Satellite host to RHEL 8 there are at least two issues that I can see which are inter-related.

1) "subscription-manager release --unset" is not run by LEAPP or "satellite-maintain", thus leaving a recently LEAPPed RHEL 8 host 'stuck' on RHEL 8.6.
2) "satellite-maintain" will not therefore update the Satellite host to more recent/current RPMs when doing updates/upgrades.

It's possible one could run the command in 1) manually after LEAPPing, but how does one then safely update the Satellite host's packages outside of an update (say from 6.11 to 6.12)?

Version-Release number of selected component (if applicable):
Satellite 6.11+

How reproducible:
Whenever a LEAPP from RHEL 7 to RHEL 8 is done.

Steps to Reproduce:
1. LEAPP RHEL 7 Satellite host
2. After reboot watch satellite-maintain update Satellite packages from RHEL 7 versions to RHEL 8 versions
3. Observe that non-Satellite RHEL 8 packages are not at 'current' due to release version being set and "dnf update" being blocked by foreman-protector plugin

Actual results:
LEAPPed RHEL 8 host's Satellite installation moved to compatible version, but remaining OS packages not at 'current' package release levels, and therefore potentially buggy/insecure

Expected results:
Host to be LEAPPed, Satellite installation moved to compatible version, and OS release unset.  Additionally host to be completely "dnf update"ed at end of process, or instructions on how to do so with satellite-maintain and foreman-protector in place.

Additional info:
Please ask.

Comment 1 Ben 2022-11-16 18:21:11 UTC

I see that after a manual "subscription-manager release --unset", "satellite-maintain upgrade check --target-version 6.11.z" upgraded the host to 8.7.  Still, there was a manual step required that someone might not know to do...

Comment 3 Ben 2023-01-23 09:44:10 UTC

What info is required of me, please?  I cannot see SAT-14962 to verify that it's useful.

Comment 4 Leos Stejskal 2023-01-27 07:38:55 UTC

Hi Ben,
as my previous command, I suggest to change to RFE, the issue described here is not a bug,
we never intended to use the playbook for end to end Satellite upgrade, just for RHEL machines.

Comment 5 Ben 2023-01-27 10:05:39 UTC

OK, an RFE it is!  I'll get one opened next week.

Comment 6 Ron Lavi 2023-01-29 13:52:55 UTC

Hi Ben, we can use this BZ as the RFE,
Added [RFE] prefix to the title + it already has the FutureFeature keyword