Bug 1274750

Summary: In the undercloud Nova's ram_allocation_ratio configuration option should be set to "1.0"
Product: Red Hat OpenStack Reporter: Lucas Alvares Gomes <lmartins>
Component: instack-undercloudAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: achernet, emacchi, hbrock, mburns, nlevinki, rhel-osp-director-maint
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: instack-undercloud-2.2.2-3.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 21:41:52 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:

Description Lucas Alvares Gomes 2015-10-23 13:42:42 UTC
Description of problem:
By default the Nova's "ram_allocation_ratio" is "1.5", this doesn't make sense for baremetal because we can't allocate more memory than the machine already has.

By leaving it as default ("1.5") will cause scheduling instances to fail in case the amount of RAM in the node's is exactly the same size in the flavor. And this should just work.


Version-Release number of selected component (if applicable):


How reproducible:
100%


Steps to Reproduce:
1. Create a flavor that requires 512MB of memory
2. Create a node (and have only one node available) in ironic that has 512MB of memory
3. Try to deploy it

Actual results:
Nova won't be able to allocate the amount of ram asked and will fail with a "no valid host found"


Expected results:
The node should be picked for deployment

Additional info:

Comment 5 errata-xmlrpc 2016-04-07 21:41:52 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://rhn.redhat.com/errata/RHEA-2016-0604.html