Bug 2039032

Summary:	[RFE] Notify users of releasever lock in subscription-manager
Product:	Red Hat Enterprise Linux 9	Reporter:	Craig Donnelly <cdonnell>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED MIGRATED	QA Contact:	Red Hat subscription-manager QE Team <rhsm-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	jcastran, pdwyer, redakkan
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
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-09-22 13:14:02 UTC	Type:	Story
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 18:28:06 UTC

Description of problem:
Currently, there is no warning for a user to know that a releasever lock has been set.

This becomes a bigger problem with implementations where the user is not the one setting the releasever.

An example is the LEAPP upgrade from 8 to 9 which in an RHSM scenario, will (attempt [assumes proper entitlement]) to set the releasever to 9.0 on the FirstBoot stage of the upgrade.

Other than reading a note somewhere, a user may not know this has occurred, and maybe be upgrading a non-extended-release system.

It would be useful to have a note printed about a releasever lock during a dnf transaction.

Whether that is from dnf-plugin-subscription-manager or a new plugin that is RHEL specific shipped (since this is RHEL specific), is undecided.

There are a few different ways to implement this, and trigger the message.
We could only trigger when there are no extended-stream entitlements, or we could always trigger as a note during a transaction. If we don't want to expose new stdout msgs, we could also add this info to rhsm.log specifically, though this will be less likely to be brought to a users attention.

Actual results:
I didn't know I had a releasever set.

Expected results:
Tell me always.

Additional info:

Comment 2 RHEL Program Management 2023-09-22 12:51:36 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-22 13:14:02 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.