Bug 1499083

Summary: [sprint] used_ram not correct, openstack create instance failed with "Cannot allocate memory"
Product: Red Hat OpenStack Reporter: Nilesh <nchandek>
Component: openstack-novaAssignee: Sahid Ferdjaoui <sferdjao>
Status: CLOSED DUPLICATE QA Contact: Joe H. Rahme <jhakimra>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: awaugama, berrange, dasmith, eglynn, kchamart, mbooth, nchandek, sbauza, sferdjao, sgordon, srevivo, stephenfin, vromanso
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-15 09:20:43 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:

Comment 2 Sahid Ferdjaoui 2017-10-06 06:49:50 UTC
(In reply to Nilesh from comment #0)
> The reason we couldn’t create the mavinir instance is that we don’t have
> enough free memory (HugePages) on p23.
> Mavenir instance needs 65536MB memory, and we only have total 21504 MB free
> huge memory left.
> 
> Then why openstack still assigns compute resource from p23 to the instance?
> why used_ram, which doesn’t tell the truth. And because of this the nova
> scheduler think we will have enough free memory left on p23, and then
> allocate the compute resource from p23 to this instance.
> 

Is the NUMATOpologyFilter well configured? is the only piece of code which is aware of the difference kind of memory pages in a system. Nova in general only care about small pages.

Comment 21 Sahid Ferdjaoui 2017-12-06 09:50:10 UTC
reopen it, time to investigate whether bug 1519540 could be a duplicate

Comment 22 Sahid Ferdjaoui 2017-12-15 09:20:43 UTC

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