Comment 9 for bug 1519878

Chck out this log, it clearly states that the issue is Numa topology requirments.

2015-11-26 10:08:39.604 2899 DEBUG nova.scheduler.filters.numa_topology_filter [req-9688c526-0f54-43f3-ba1a-7fe1d1bc63d4 d525cf27fd9c4782a20363f65bed9795 f77fb93ac01c488f8cfd1eb4ebe7c2f0 - - -] sbezverk-osp-4.sbezverk.cisco.com, sbezverk-osp-4.sbezverk.cisco.com fails NUMA topologyrequirements. The instance does not fit on this host. host_passes /usr/lib/python2.7/site-packages/nova/scheduler/filters/numa_topology_filter.py:48

2015-11-26 10:08:39.605 2899 INFO nova.filters [req-9688c526-0f54-43f3-ba1a-7fe1d1bc63d4 d525cf27fd9c4782a20363f65bed9795 f77fb93ac01c488f8cfd1eb4ebe7c2f0 - - -] Filter NUMATopologyFilter returned 0 hosts
2015-11-26 10:08:39.605 2899 DEBUG nova.filters [req-9688c526-0f54-43f3-ba1a-7fe1d1bc63d4 d525cf27fd9c4782a20363f65bed9795 f77fb93ac01c488f8cfd1eb4ebe7c2f0 - - -] Filtering removed all hosts for the request with reservation ID 'r-tfsr0m79' and instance ID 'd4643825-0893-45b9-904d-b5a6bbd1ec30'. Filter results: [('RetryFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('AvailabilityZoneFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('RamFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('ComputeFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('ComputeCapabilitiesFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('ImagePropertiesFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('ServerGroupAntiAffinityFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('ServerGroupAffinityFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('PciPassthroughFilter', [(u'sbezverk-osp-4.sbezverk.cisco.com', u'sbezverk-osp-4.sbezverk.cisco.com')]), ('NUMATopologyFilter', None)] get_filtered_objects /usr/lib/python2.7/site-packages/nova/filters.py:122
2015-11-26 10:08:39.605 2899 INFO nova.filters [req-9688c526-0f54-43f3-ba1a-7fe1d1bc63d4 d525cf27fd9c4782a20363f65bed9795 f77fb93ac01c488f8cfd1eb4ebe7c2f0 - - -] Filtering removed all hosts for the request with reservation ID 'r-tfsr0m79' and instance ID 'd4643825-0893-45b9-904d-b5a6bbd1ec30'. Filter results: ['RetryFilter: (start: 1, end: 1)', 'AvailabilityZoneFilter: (start: 1, end: 1)', 'RamFilter: (start: 1, end: 1)', 'ComputeFilter: (start: 1, end: 1)', 'ComputeCapabilitiesFilter: (start: 1, end: 1)', 'ImagePropertiesFilter: (start: 1, end: 1)', 'ServerGroupAntiAffinityFilter: (start: 1, end: 1)', 'ServerGroupAffinityFilter: (start: 1, end: 1)', 'PciPassthroughFilter: (start: 1, end: 1)', 'NUMATopologyFilter: (start: 1, end: 0)']

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Nikola Ðipanov
Sent: Thursday, November 26, 2015 11:04 AM
To: Serguei Bezverkhi (sbezverk) <email address hidden>
Subject: [Bug 1519878] Re: numatopology filter incorrectly returns no resources

Hey so I was not able to reproduce this - the Nova pinning logic seems to pass this (I was testing it with 12.0.0 tag checked out) see the attached patch.

Are you sure that it's the NUMA topology filter that was failing. It might be best to turn on debug logging in the scheduler and make sure that it's the NUMATopologyFilter that is returning 0 hosts

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1519878

Title:
  numatopology filter incorrectly returns no resources

Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  When launching a new instance, in some cases NUmaTopology Filter does
  not return available compute nodes, but according to the content of
  numa_topology in compute_nodes tables, there are sufficient resources
  to satisfy requirements.

  I started three instances, attached log show changes in numa_topology,
  when I try to start 4th instance which is requesting 4vCPU and
  according to numa_topology I have left 8 vCPU, NumaTopology filter
  incorrectly returns 0 hosts. If I delete existing instances, I can
  launch failed one without any modification.

  rpm -qa | grep nova
  openstack-nova-conductor-12.0.0-1.el7.noarch
  python-novaclient-2.30.1-1.el7.noarch
  openstack-nova-console-12.0.0-1.el7.noarch
  openstack-nova-common-12.0.0-1.el7.noarch
  openstack-nova-scheduler-12.0.0-1.el7.noarch
  openstack-nova-compute-12.0.0-1.el7.noarch
  python-nova-12.0.0-1.el7.noarch
  openstack-nova-novncproxy-12.0.0-1.el7.noarch
  openstack-nova-api-12.0.0-1.el7.noarch
  openstack-nova-cert-12.0.0-1.el7.noarch

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