Bug 2282249

Summary:	Subscription Allocation type for Red Hat Satellite server reverts to an incorrect version after refreshing Manifest
Product:	Red Hat Satellite	Reporter:	Alexon Oliveira <alolivei>
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.12.2	CC:	aruzicka, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
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:39:57 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 Alexon Oliveira 2024-05-21 20:08:52 UTC

Description of problem:

After upgrading Satellite from 6.10 to 6.11 and then 6.12, when running a refresh of the manifest, the Subscription Allocation type, which indicates the Satellite version to be used, is changed automatically to 6.15, which causes a failure in Satellite to identify and enable any repository. This seems pretty much a bug regression of the following, with the difference of getting the version higher, not lower:

https://access.redhat.com/solutions/5039851

https://bugzilla.redhat.com/show_bug.cgi?id=1823905


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

6.12.z

How reproducible:

Upgrading from 6.10, to 6.11 and then 6.12. Bug not found in a fresh install.

Steps to Reproduce:

1. Upgrade Satellite from 6.10, to 6.11 and finally 6.12, changing the Subscription Allocation type accordingly along the way.
2. When in 6.12, click the Refresh button to refresh the Manifest.
3. Check the Subscription Allocation type and the version will be set as 6.15.
4. Satellite will throw a SSL error accusing the version to be wrong and no repository is able to be accessed or enabled.

Actual results:

Refreshing a Manifest is automatically changing the Subscription Allocation type.

Expected results:

The Subscription Allocation type should only be changed manually, not after a Manifest refresh in Satellite.

Additional info:

Comment 2 Eric Helms 2024-06-06 17:39:57 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.