Bug 1625120 - [rhos13] nova reporting incorrect available memory
Summary: [rhos13] nova reporting incorrect available memory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z3
: 13.0 (Queens)
Assignee: OSP DFG:Compute
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On: 1569678 1625122
Blocks: 1519540 1625119 1664701
TreeView+ depends on / blocked
 
Reported: 2018-09-04 07:42 UTC by Sahid Ferdjaoui
Modified: 2023-03-21 18:59 UTC (History)
19 users (show)

Fixed In Version: openstack-nova-17.0.6-2.ddb90b8git.el7ost
Doc Type: Bug Fix
Doc Text:
Cause: When booting an instance with huge pages, nova did not consider the NUMA affinity of huge pages when determining if an instance could fit on the host. Consequence: An error would be raised when booting a instance on a host NUMA node with insufficient huge pages. Fix: Nova now considers NUMA affinity of host huge pages when booting instances with huge pages. Result: Hosts NUMA nodes that have sufficient CPUs but insufficient huge pages will now be rejected.
Clone Of: 1625119
: 1625122 (view as bug list)
Environment:
Last Closed: 2018-11-13 22:13:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1734204 0 None None None 2018-09-04 07:42:52 UTC
OpenStack gerrit 532168 0 None MERGED hardware: fix memory check usage for small/large pages 2020-12-22 00:46:57 UTC
Red Hat Issue Tracker OSP-5102 0 None None None 2022-08-16 08:44:37 UTC
Red Hat Product Errata RHBA-2018:3602 0 None None None 2018-11-13 22:16:14 UTC

Comment 11 errata-xmlrpc 2018-11-13 22:13:45 UTC 
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, 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-2018:3602
Note You need to log in before you can comment on or make changes to this bug.