Bug 2039081

Summary:	LEAPP should not set a releasever on completion of upgrade to RHEL 9
Product:	Red Hat Enterprise Linux 8	Reporter:	Craig Donnelly <cdonnell>
Component:	leapp-repository	Assignee:	Petr Stodulka <pstodulk>
Status:	CLOSED WONTFIX	QA Contact:	Martin Klusoň <mkluson>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8.6	CC:	fkrska, jcastran, jsefler, podvody, pstodulk, tbowling
Target Milestone:	rc
Target Release:	---
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-07-10 07:28:09 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 Craig Donnelly 2022-01-10 21:55:21 UTC

Description of problem:
When completing an upgrade from RHEL 8.6 to 9.0 builds, the FirstBoot phase of LEAPP in RHSM mode attempts to set the RHSM Release (releasever) statically to 9.0.

This should not be desired behavior, unless the customer already has a similar configuration in place. For instance, I might expect that if a customer is releasever locked to RHEL 8.6 with EUS repositories enabled, then perhaps I may lock this customers release to 9.0 - with EUS repositories enabled for 9.0 on the resulting upgraded system.

I do not however expect a normal 8.6.z system to be upgraded to RHEL 9 and then releasever locked to RHEL 9.0

This has the potential to create unnecessary confusion and customer cases in regards to being unable to update packages to newer releases.

Version-Release number of selected component (if applicable):
python3-leapp-0.13.0-100.20211223153804354186.master.6.gfb91abd.el8.noarch
leapp-upgrade-el8toel9-0.15.0-100.20220104155018578811.master.37.gf2026d2.el8.noarch
leapp-0.13.0-100.20211223153804354186.master.6.gfb91abd.el8.noarch
leapp-repository-deps-el9-5.0.9-100.202201041550Z.f2026d2.master.el9.noarch
leapp-deps-el9-5.0.9-100.202201041550Z.f2026d2.master.el9.noarch

How reproducible:
100% with RHSM mode.

Steps to Reproduce:
1. Entitle system properly for RHEL 8
2. Perform leapp upgrade from 8 -> 9.
3. Await FirstBoot phase.

Actual results:
Tries or succeeds to set releasever to 9.0.

Expected results:
Release should be unset when upgrade is complete.

Additional info:

Comment 1 Petr Stodulka 2022-01-11 10:31:00 UTC

Hi Craig! Thanks for the report. We are happy to sync with you about this problem as from our understanding the missing lock is more problematic. Imagine situation when a newer version of OS is released in general (e.g. 9.1, 9.2, ...). Customers usually needs the specific target OS release because of certifications. Running `dnf update` command after the upgrade when newer releases are present means that customers are running on non-certified system usually and it's pretty hard to get back (imagine now people upgrading to 8.4 with E4S (SAP) and than install stuff from RHEL 8.5...). The same is applied for upgrades 7 -> 8. Feel free to schedule a mtg during the next week to sync about that. Invite please also Pavel Odvody.

Comment 7 RHEL Program Management 2023-07-10 07:28:09 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.