Bug 1795361 - Subscription Watch RHEL Capacity Double Expected Value
Summary: Subscription Watch RHEL Capacity Double Expected Value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Hybrid Cloud Console (console.redhat.com)
Classification: Red Hat
Component: Subscription Watch
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Kevin Howell
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-27 19:00 UTC by dozdowsk
Modified: 2020-05-29 07:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-05 15:24:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github RedHatInsights rhsm-subscriptions pull 93 0 None closed Divide effective capacity by instance_multiplier 2020-12-02 12:56:03 UTC

Description dozdowsk 2020-01-27 19:00:40 UTC
Description of problem:
Capacitor is representing double RHEL x86 capacity for a customer

Version-Release number of selected component (if applicable):
Bug crosses multiple releases of Capacitor


How reproducible:
Always

Steps to Reproduce:
A customer who reached out to me directly has 18x socket pair subscriptions of RH00003/4 which should indicate 36 sockets of capacity.  Their capacity is being drawn at 72 sockets - which is double what is expected.

1. Open RHSM and check available subscriptions for account (number included privately)
2. Open Subscription Watch for account

Actual results:
72 sockets of RHEL x86 capacity


Expected results:
36 sockets of RHEL x86 capacity

Additional info:
Customer reached out directly to PM through the Accelerators program

Comment 3 Nikhil Kathole 2020-04-17 12:00:50 UTC
VERIFIED

Env : CI

Adding 18 quantity of RH00003 increases 36 Premium sockets of RHEL capacity.

Adding 18 quantity of RH00004 increases 36 Standard sockets of RHEL capacity.


Note You need to log in before you can comment on or make changes to this bug.