e1783b0087
When making a GET /allocation_candidates request with the 'limit' parameter, include all the providers in the same tree as the providers mentioned in the allocation requests. That is, in a nested situation, if we limit the allocation requests to 10, we would usually expect considerably more than 10 providers in provider summaries, to include any non-contributing providers in the same tree. Accomplish this by filtering provider summaries on root_provider_uuid instead of individual provider uuid. A gabbi test is added which exercises this in a nested situation. An existing test is updated to reflect the new filtering style. It does not exercise the nested scenario. A reno is added indicating the fix. Change-Id: I136bd7cd89f1bd54f0d1691268545850af234f18 Story: 2005859 Task: 33654
12 lines
506 B
YAML
12 lines
506 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Limiting nested resource providers with the ``limit=N`` query parameter
|
|
when calling ``GET /allocation_candidates`` could result in incomplete
|
|
provider summaries. This is now fixed so that all resource providers that
|
|
are in the same trees as any provider mentioned in the limited allocation
|
|
requests are shown in the provider summaries collection. For more
|
|
information see `story/2005859`_.
|
|
|
|
.. _story/2005859: https://storyboard.openstack.org/#!/story/2005859
|