yahoo-eng-team team mailing list archive

[Alvaro Uría <1751784@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I'm running xenial-mitaka but I see a similar code in master branch.

Nodes get filtered because of NUMATopologyFilter:
"""
2018-02-26 11:23:48.435 197208 DEBUG nova.scheduler.filters.numa_topology_filter
 [req-17b0859a-8805-4d65-bc64-786c31827437 6a9c32b9567c451e99fd46a8eb7f924b e8103cf138ae4902a08461a38c85a6dc - - -]
 [instance: 44ee035e-6d15-4b8c-ad86-aec5282b04d5] Hypervisor-Compute-10, Hypervisor-Compute-10.maas fails NUMA topology
 requirements. The instance does not fit on this host. host_passes /usr/lib/python2.7/dist-packages/nova/scheduler/filters/numa_topology_filter.py:91
"""

This filter is difficult to troubleshoot because there are not much
LOG.debug functions in nova.virt.hardware.

In this case, hypervisors are filtered after running:
https://github.com/openstack/nova/blob/master/nova/virt/hardware.py#L1431

But I don't know exactly what didn't match the expected resources.

For background purposes, nodes run hugepages, they have enough cpu/mem/disk resources and flavor extra_spec matches host aggregate extra_spec. Flavor also specifies the following properties:
"""
hw:cpu_policy='dedicated', hw:cpu_thread_policy='prefer', hw:mem_page_size='1048576'
"""

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: canonical-bootstack

-- 
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/1751784

Title:
  Add more LOG.debug in nova.virt.hardware

Status in OpenStack Compute (nova):
  New

Bug description:
  I'm running xenial-mitaka but I see a similar code in master branch.

  Nodes get filtered because of NUMATopologyFilter:
  """
  2018-02-26 11:23:48.435 197208 DEBUG nova.scheduler.filters.numa_topology_filter
   [req-17b0859a-8805-4d65-bc64-786c31827437 6a9c32b9567c451e99fd46a8eb7f924b e8103cf138ae4902a08461a38c85a6dc - - -]
   [instance: 44ee035e-6d15-4b8c-ad86-aec5282b04d5] Hypervisor-Compute-10, Hypervisor-Compute-10.maas fails NUMA topology
   requirements. The instance does not fit on this host. host_passes /usr/lib/python2.7/dist-packages/nova/scheduler/filters/numa_topology_filter.py:91
  """

  This filter is difficult to troubleshoot because there are not much
  LOG.debug functions in nova.virt.hardware.

  In this case, hypervisors are filtered after running:
  https://github.com/openstack/nova/blob/master/nova/virt/hardware.py#L1431

  But I don't know exactly what didn't match the expected resources.

  For background purposes, nodes run hugepages, they have enough cpu/mem/disk resources and flavor extra_spec matches host aggregate extra_spec. Flavor also specifies the following properties:
  """
  hw:cpu_policy='dedicated', hw:cpu_thread_policy='prefer', hw:mem_page_size='1048576'
  """

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