Bug 2178845

Summary:	Red Hat Custom Portal - Subscription Allocations for Satellite 6.12 manifest profile only shows 'Satellite 6'
Product:	Red Hat Satellite	Reporter:	Ricardo Santamaria <risantam>
Component:	Candlepin	Assignee:	Barnaby Court <bcourt>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.12.1	CC:	nmoumoul
Target Milestone:	Unspecified	Keywords:	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:	2023-03-22 13:36:04 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 Ricardo Santamaria 2023-03-15 21:11:30 UTC

Description of problem:
Red Hat Custom Portal - Subscription Allocations for Satellite 6.12 manifest profile only shows 'Satellite 6' vs. the full 'Satellite 6.12' version that is seen once you click into the manifest profile. 

Version-Release number of selected component (if applicable):
Satellite 6.12 (in this current scenario) 

How reproducible:
n/a

Steps to Reproduce:
1. Log into Customer Portal to view Subscription Allocations
2. Note 'Type' column states 'Satellite 6'
then to correct:
3. Click on manifest profile 'Name' 
4. Verify 'Type' here correctly displays 'Satellite 6.12'
(SCA is disabled)
5. Click drop down to once more select 'Satellite 6.12' 
6. Click Update button

7. Returning to 'Subscription Allocations' page find 'Type' column is now corrected

After an undetermined amount of time the 'Type' at this page reverts to 'Satellite 6'. Above steps will work again until reverts to 'Satellite 6' type again. 



Expected results:
'Type' when looking at 'Subscription Allocations' should match the type of the manifest 

Additional info:

Comment 1 Nikos Moumoulidis 2023-03-22 13:36:04 UTC

Closing this as duplicate of 2168330.
Until the fix is available you can work around it by deleting your allocation and recreating it.

*** This bug has been marked as a duplicate of bug 2168330 ***