Bug 2269998

Summary:	Subscription-manager release --unset doesn't reset the client information on Red Hat Satellite
Product:	Red Hat Satellite	Reporter:	Avnish Kumar <avnkumar>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.14.2	CC:	ahumbe, chrobert, jpasqual, Ken.Fowler, rlavi
Target Milestone:	Unspecified	Keywords:	EasyFix, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:26: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 Avnish Kumar 2024-03-18 04:33:45 UTC

Description of problem:
Subscription-manager release --unset doesn't reset the client information on Red Hat Satellite

Version-Release number of selected component (if applicable):
Satellite 6.x

How reproducible:
Unset Subscription-manager release on the client and check info on satellite.

Steps to Reproduce:
1. Subscription-manager release --unset
2. Subscription-manager release --show
3. Subscription-manager facts --update

Actual results:
Release Version remains the same on the satellite DB

Expected results:
Release Version should be updated on the satellite

Additional info:
Also Subscription-manager facts --update doesn't refresh release information

Comment 5 Eric Helms 2024-05-16 16:18:20 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/37358 has been resolved.

Comment 6 Eric Helms 2024-06-06 17:26:09 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 "SAT-" 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.