Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1625120

Summary: [rhos13] nova reporting incorrect available memory
Product: Red Hat OpenStack Reporter: Sahid Ferdjaoui <sferdjao>
Component: openstack-novaAssignee: OSP DFG:Compute <osp-dfg-compute>
Status: CLOSED ERRATA QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: berrange, coldford, cswanson, dasmith, dvd, eglynn, jhakimra, jschluet, kchamart, marjones, mbooth, mmethot, nova-maint, rosingh, sbauza, sgordon, srevivo, stephenfin, vromanso
Target Milestone: z3Keywords: Reopened, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
 Story Points: ---
Clone Of: 1625119
: 1625122 (view as bug list) Environment:
Last Closed: 2018-11-13 22:13:45 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:
Bug Depends On: 1569678, 1625122    
Bug Blocks: 1519540, 1625119, 1664701    

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