Bug 2091455

Summary:	In Subscription Watch, all VDC/Hosts subscriptions from different platforms are combined, this needs to be breakdown
Product:	Red Hat Hybrid Cloud Console (console.redhat.com)	Reporter:	jalviso <jalviso>
Component:	Subscription Watch	Assignee:	Kevin Howell <khowell>
Status:	CLOSED DUPLICATE	QA Contact:	Jon Allen <jallen>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	andrew.rietkerk, hhudgeon, nkathole, sghai, sjagtap, wpinheir
Target Milestone:	---	Keywords:	RFE, Triaged
Target Release:	---
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:	2022-08-01 18:47:45 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 jalviso 2022-05-30 01:14:09 UTC

Description of problem:

The VDC/host subscriptions are aggregated between platforms, but each platform uses a different subscription. For example ppc64le on OpenStack has a different subscription to a non-OpenStack ppc64le host. 
Similar, for x86, an OpenStack x86 VDC compute node requires a different subscription to a VDC node on VMware. We cannot tell the total subscriptions required for each platform/type of subscription. Also applies to Bare Metal and OpenStack Baremetal.

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

How reproducible: Always

Steps to Reproduce:

1. In Subscription Watch, https://console.redhat.com/insights/subscriptions/rhel
   
2. Locate "Physical RHEL" or "Virtualized RHEL" nodes that are consuming OpenStack, RHEV of VDC

Actual results:

All hypervisor nodes from different platforms are combined: VMware Hypervisors, Openstack (or OpenStack Baremetal), RHEV, Baremetal

Expected results:

Hypervisors from different platforms should be segregated to identify what Hosts consumes what subscriptions. Or a way to filter different types of hypervisor node
will be useful.

Additional info:

Currently, it is very hard to identify what nodes are consuming the Hypervisor-based subscription. The fact that Subscription Watch puts them in one "bucket" is no use when using the information to renew subscriptions.

Comment 5 Hayley Hudgeons 2022-08-01 17:57:44 UTC

This bugzilla has migrated to Jira. Please reference the attached Jira to continue tracking the issue comments and status.

Comment 6 Hayley Hudgeons 2022-08-01 18:47:45 UTC


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