Bug 1274750 - In the undercloud Nova's ram_allocation_ratio configuration option should be set to "1.0"
Summary: In the undercloud Nova's ram_allocation_ratio configuration option should be ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Lucas Alvares Gomes
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-23 13:42 UTC by Lucas Alvares Gomes
Modified: 2016-04-07 21:41 UTC (History)
6 users (show)

Fixed In Version: instack-undercloud-2.2.2-3.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-07 21:41:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 255821 0 None None None Never
Red Hat Product Errata RHEA-2016:0604 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 director Enhancement Advisory 2016-04-08 01:03:56 UTC

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


Note You need to log in before you can comment on or make changes to this bug.