yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1674300@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674300

Title:
  Cannot spin an instance because the NUMATopology Filter Returned 0
  Hosts

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description
  ===========
  I am unable to launch an instance which requests for 16vCPUs dedicated (CPU Pinning) and 232 GB of RAM. The request fails all the time with "Filter NUMATopologyFilter returned 0 hosts". The blade server has 28 vCPUs available and 240 GB of RAM available. 

  Paste #603395 - Has the error and exception that I see in nova-
  all.log.

  The blade server where I am trying to create this instance has the
  below configuration-

  root@RTPCLABQPS1H-3-1:~# numactl --hardware
  available: 2 nodes (0-1)
  node 0 cpus: 0 1 2 3 4 5 6 7 8 9 20 21 22 23 24 25 26 27 28 29
  node 0 size: 193386 MB
  node 0 free: 186836 MB
  node 1 cpus: 10 11 12 13 14 15 16 17 18 19 30 31 32 33 34 35 36 37 38 39
  node 1 size: 193533 MB
  node 1 free: 191822 MB
  node distances:
  node   0   1
    0:  10  20
    1:  20  10
  root@RTPCLABQPS1H-3-1:~#

  
  Steps to reproduce
  ==================
  1. Try to create instance using nova, web or heat - with 16 vCPUs and 232 GB RAM
  2. I receive an error that 0 Hosts are returned by NUMATOPOLOGY Filter
      ~ nova --debug boot - complete log at http://paste.openstack.org/show/603398/

  
  Expected result
  ===============
  The instance should be created without any issue because the blade server has 28 vCPUs available and 240 GB RAM.

  
  Actual result
  =============
  The instance creation failed with- NUMATopology Filter Returned 0 Hosts

  
  Environment
  ===========
  1. Openstack KILO
  root@RTPCLABQPS1H-CC-A:/var/log/nova# dpkg -l | grep nova
  ii  nova-api                            1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - compute API frontend
  ii  nova-cert                           1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - certificate manager
  ii  nova-common                         1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - common files
  ii  nova-conductor                      1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - conductor service
  ii  nova-consoleauth                    1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - Console Authenticator
  ii  nova-consoleproxy                   1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - NoVNC proxy
  ii  nova-objectstore                    1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - object store
  ii  nova-scheduler                      1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - virtual machine scheduler
  ii  python-nova                         1:2015.1.1-1~u14.04+mos19695           all          OpenStack Compute - libraries
  ii  python-novaclient                   1:2.23.0-1~u14.04+mos1247              all          client library for OpenStack Compute API

  2. Libvirt + KVM Version 
  root@RTPCLABQPS1H-3-1:~# kvm --version
  QEMU emulator version 2.4.0 (Debian 1:2.4+dfsg-ubuntu3), Copyright (c) 2003-2008 Fabrice Bellard

  3. Networking Type - Neutron

  4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1674300/+subscriptions