yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => kilo-3

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

Title:
  Instance's numa_topology shouldn't be changed in NUMATopologyFilter

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  In change https://review.openstack.org/#/c/133998, the
  instance['numa_topology'] will be set when filter successfully. when
  we have many hosts in environment, the instance['numa_topology'] will
  be set every time when filter host successfully, and it will be the
  numa_topology that base on last fitting successfully host's
  numa_topology. But the instance may will don't boot on the last
  filtered host after weighting and random selecting. That may lead
  booting failed because the numa_topology of "last filtered host" may
  be different with the chosen host's.

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