Bug 1885822

Summary: After Q3 release of Subscription Watch, some physical systems and hypervisors showing mismatch in socket count in subscription watch and insights inventory
Product: Red Hat Hybrid Cloud Console (console.redhat.com) Reporter: sgajendr
Component: Subscription WatchAssignee: Kevin Howell <khowell>
Status: CLOSED CURRENTRELEASE QA Contact: Jon Allen <jallen>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: dozdowsk, nkathole, sghai
Target Milestone: ---Keywords: Triaged
Target Release: ---   
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: 2020-12-03 03:33:14 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:
Attachments:
Description Flags
subscription-watch socket mismatch data none

Description sgajendr 2020-10-07 04:41:23 UTC 
Created attachment 1719557 [details]
subscription-watch socket mismatch data

Description of problem:

After Q3 release  of Subscription Watch, we are able to see systems socket contribution in subscription-watch . In some physical systems and hypervisors , socket count is showing mismatch in subscription watch and insights inventory.

Version-Release number of selected component (if applicable):
After Q3 release of subscription-watch 

How reproducible:


Steps to Reproduce:
1.Login to subscription watch by using URL:https://cloud.redhat.com/subscriptions/rhel-sw/all
2.Check the socket count of system in subscription-watch.
3.Check the socket count of system in insights inventory by clicking profile of system.

Actual results:
socket count of system in subscription-watch reflecting as 2
socket count of system in insights inventory of same system profile reflecting as 1


Expected results:
socket count of system in subscription-watch and in insights inventory should be same and should not mismatch

Additional info:
Please check attachment where we have provided screenshot of some of physical systems and hypervisors in Red Hat  account whose socket count in subscription-watch and insight inventory are mismatched
Comment 1 Nikhil Kathole 2020-10-07 05:07:14 UTC 
Hi,

Subscription watch measures your physical RHEL installations by CPU socket pairs. Please look into docs for detailed explanation: https://access.redhat.com/documentation/en-us/subscription_central/2020-10/html-single/getting_started_with_subscription_watch/index#con-how-does-subscriptionwatch-show-data_assembly-opening-subscriptionwatch-ctxt 

Reference from doc:

Consumption of sockets or cores in the inventory application is represented as actual consumption. Usage in subscription watch is represented as normalized consumption, bound by the terms of subscription. For example, usage of a physical RHEL subscription is measured by socket pair, so a socket count for that type of system is always rounded to the next higher even number. 

Hope this helps. Let us know if you have any other questions.

Thanks.
Comment 3 Nikhil Kathole 2020-12-03 03:33:14 UTC 
Fixed in 02-12-2020 release with https://github.com/RedHatInsights/curiosity-frontend/issues/483.

Terminology changed from sockets to "Subscribed sockets" in Subs Watch UI to be more clear.
Comment 4 Red Hat Bugzilla 2023-09-14 06:09:12 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days