Finally was able to get some time to look more into the log files
On Mon, Jun 20, 2016 at 10:52 PM, Gerard Braad <me(a)gbraad.nl> wrote:
On Mon, Jun 20, 2016 at 10:34 PM, John Trowbridge
<trown(a)redhat.com> wrote:
> I usually grep for 'returned 0 host' to find which filter is failing
after the Compute capability filter:
2016-06-20 09:15:18.275 1186 DEBUG nova.filters
[req-665aaa1f-7788-4aea-85cd-c08097d934c5
0b48c6614e73469eb2350fe09c33ee10 2fea396ebcab48ed8c150ef31506f66f - -
-] Filter ComputeCapabilitiesFilter returned 1 host(s)
get_filtered_objects
/usr/lib/python2.7/site-packages/nova/filters.py:104
It seems a node that claims to have less than 4G of memory. The node
actually contains 64G of memory and this is also reported by the
introspection (node-show)
2016-06-20 09:15:18.276 1186 DEBUG nova.scheduler.filters.ram_filter
[req-665aaa1f-7788-4aea-85cd-c08097d934c5
0b48c6614e73469eb2350fe09c33ee10 2fea396ebcab48ed8c150ef31506f66f - -
-] (undercloud, 0956df36-b642-44b8-a67f-0df88270372b) ram: 0MB disk:
0MB io_ops: 0 instances: 0 does not have 4096 MB usable ram before
overcommit, it only has 0 MB. host_passes
/usr/lib/python2.7/site-packages/nova/scheduler/filters/ram_filter.py:45
2016-06-20 09:15:18.276 1186 INFO nova.filters
[req-665aaa1f-7788-4aea-85cd-c08097d934c5
0b48c6614e73469eb2350fe09c33ee10 2fea396ebcab48ed8c150ef31506f66f - -
-] Filter RamFilter returned 0 hosts
--
Gerard Braad |
http://gbraad.nl
[ Doing Open Source Matters ]