Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2021624

Summary:	[RFE] SKU's that are not in whitelist causing problems and doubts for the customers regarding to threshold
Product:	Red Hat Hybrid Cloud Console (console.redhat.com)	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Subscription Watch	Assignee:	Kevin Howell <khowell>
Status:	CLOSED DEFERRED	QA Contact:	Jon Allen <jallen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	hhudgeon, jkreft, khowell, rjerrido, sghai, sjagtap
Target Milestone:	---	Keywords:	FutureFeature, RFE, Triaged
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:	2022-08-01 17:29:38 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 Waldirio M Pinheiro 2021-11-09 19:08:19 UTC

Description of problem:
Once the Swatch is not checking the whole list of SKU's that we have currently, the threshold gets wrong, and hard to explain why the value is far far away from the subs that the customer has.

We will add here all the cases that are causing issues/doubts/questions regarding Subscriptions/Swatch and Threshold.

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


How reproducible:
100%

Steps to Reproduce:
1. Use an account that has a subscription that is not in the whitelist
2. Check the swatch
3.

Actual results:
That subscription/(sockets for that) will not be counted

Expected results:
create the sockets reference for that subscription and count/display in Subscription

Additional info:
Definitely, removing the whitelist from this process and allowing Subscription to consume the whole list of SKU should be the best approach here. Maybe, creating a list/information of subscriptions that are not yet counted properly. However, the customer will be able to track/see all the subs that Subscriptions is checking/looking for.

Comment 5 Hayley Hudgeons 2022-08-01 17:29:38 UTC

This bugzilla has migrated to Jira and is awaiting prioritization by Product Management. Please reference the attached Jira to continue tracking the issue comments and status.