Description of problem: When checking Hypervisor status with Admin --> Compute --> Hypervisors in dashboard, pCPU usage information is not included when configured cpu_dedicated_set in nova.conf, such as: [compute] cpu_shared_set = 0,1,4,5 cpu_dedicated_set = 2,3,6,7 https://specs.openstack.org/openstack/nova-specs/specs/train/implemented/cpu-resources.html Version-Release number of selected component (if applicable): - RHOSP16 How reproducible: Steps to Reproduce: 1. Configure vCPU and pCPU settings in nova.conf: [compute] cpu_shared_set = 0,1,4,5 cpu_dedicated_set = 2,3,6,7 2. Create instances on above compute node 3. Check Hypervisors status in dashboard with Admin --> Compute --> Hypervisors Actual results: Only show total vCPU numbers Expected results: pCPU usage also should be included Additional info:
From the Compute point of view information about vCPUs and pCPUs is consumable via the Placement API, and is accessible on the command line with the `openstack resource provider` series of commands, as Francois pointed out in comment #5. We've 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 do not intend to re-add anything back to it. It is up to the Horizon team if and how they want to present the information from the Placement resource providers APIs in the UI. [1] https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-wallaby
*** Bug 2016832 has been marked as a duplicate of this bug. ***
Hi Team, Good day. So may understand that the fix would be included in RHOSP 18.0 ? Regards Sam
Sadly, it's not a fix, it's a feature that requires new code. We have it initially planned for osp18, but as you can see, it hasn't been ack-ed by PM yet, so it may still change.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 17.1.3 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2024:2741