yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Changed in: nova
   Importance: Undecided => High

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Changed in: nova/queens
       Status: New => Triaged

** Changed in: nova/queens
   Importance: Undecided => High

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

Title:
  ‘limit’ in allocation_candidates where sometimes make fore_hosts
  invalid

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) queens series:
  Triaged

Bug description:
     Now 'limit' parameter in allocation_candidates api use default value 1000, this makes better performace in large scale environment. However, when creating a vm/bm with force_hosts to schedule, 'limit' parameter will cut some nodes out in allocation_candidates, and sometimes force_hosts method returns 'No hosts matched due to not matching...'
  Example:
     test environment with 10 compute nodes, set max_placement_results = 3
     nova boot test --image 9c09cb52-03b9-4631-898d-d443d0dbbf9e  --flavor c1 --nic none --availability-zone nova:devstack
     No hosts matched due to not matching 'force_hosts' value of 'devstack'

     Debug:
     return provider_summaries:
     {u'268a3d69-6cf1-418a-aaa8-f2127f4f4468':...,u'a2c3e9e7-53a6-4e15-b150-39bb4135c6a9':...u'0aa80b5e-a0fa-47a6-a4b5-51b21b721ce9':...}
     and node devstack:69d2fe55-e391-4d99-a1fe-8b0b5aad60e7 not in provider_summaries.
     I think in large scale environment(compute nodes > 2000), and set default max_placement_results=1000 will make force_hosts unavailable.

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