RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1214545 - undercloud nova.conf needs reserved_host_memory_mb=0
Summary: undercloud nova.conf needs reserved_host_memory_mb=0
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: instack-undercloud
Version: Kilo
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-23 03:50 UTC by Steve Baker
Modified: 2016-05-19 15:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:53:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Steve Baker 2015-04-23 03:50:25 UTC
Description of problem:
Instack undercloud nova is configured for the default reserved_host_memory_mb=512 which means if there is the exact ironic resources required to deploy the overcloud, the deployment will fail due to the hypervisor memory used data getting 512 added for each node

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

How reproducible:
In Quintupleo, always.

Steps to Reproduce:
1. Install undercloud and register ironic nodes
2. In the undercloud, run "nova hypervisor-stats"
3.

Actual results:
memory_mb_used total is 512 * count

Expected results:
memory_mb_used=0

Additional info:
Previous undercloud templates did this [1], so I assume it is just a matter of setting the right nova::compute puppet config option

[1] http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/undercloud-vm-ironic-config.yaml#n18

Comment 1 Ben Nemec 2015-04-23 20:25:54 UTC
Not sure how this isn't breaking all virt-based environments, but it will be fixed by https://review.gerrithub.io/231005

Comment 4 Chandan Kumar 2016-05-19 15:53:12 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


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