Bug 2016832 - [OSP16.2.1][Horizon] - It is possible to use more vcpus than the limit shows
Summary: [OSP16.2.1][Horizon] - It is possible to use more vcpus than the limit shows
Keywords:
Status: CLOSED DUPLICATE of bug 1846881
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 16.2 (Train)
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: ikanias
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-24 14:36 UTC by ikanias
Modified: 2022-08-08 12:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-03 13:38:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vcpus number in flavor page (32.56 KB, image/png)
2021-10-24 14:36 UTC, ikanias
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-10539 0 None None None 2022-08-08 12:10:12 UTC

Description ikanias 2021-10-24 14:36:45 UTC
Created attachment 1836509 [details]
vcpus number in flavor page

Description of problem:
It is possible to use more vcpus than the limit shows.

Version-Release number of selected component (if applicable):
core_puddle=RHOS-16.2-RHEL-8-20211013.n.1

How reproducible:
always

Steps to Reproduce:
1. Add new flavor with 1 vcpu --> Add another flavor with 3 vcpus --> Add a third flavor with 2 vcpus
2. Add a new instance --> Attach the first flavor to the instance 
3. Open the instance from step 2 --> Attach the second flavor from step 1 --> Save
4. Open the instance from step 2 --> Attach the third flavor from step 1 --> Save
5. Go to Admin tab --> Compute --> Hypervisors --> Check the vcpus pie chart

Actual results:
The vcpus pie chart shows 'Used 6 of 4' vcpus(!)

Expected results:
It will not be possible to add more vcpus than the limit (in this case 4)

Additional info:

Comment 2 Radomir Dopieralski 2021-10-28 14:50:02 UTC
Horizon is not responsible for enforcing limits. Moving to Nova.

Comment 3 Artom Lifshitz 2021-11-01 14:15:56 UTC
I suspect this is coming from Horizon using the hypervisors API instead of querying the Placement resource providers? In that sense, this is similar to BZ 1846881, where I've said that Nova has made a point of removing usage information from the `hypervisors` API [1] as it was "frequently misleading or outright wrong [and] can be better queried from placement" - and we do not intend to re-add anything back to it. I'm moving this back to Horizon, feel free to close as a duplicate of 1846881.

[1] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-wallaby

Comment 4 Radomir Dopieralski 2021-11-03 13:38:52 UTC

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


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