c85ae69ee9
When placement picks up allocation candidates, the aggregates of nested providers were assumed as the same as root providers. This means that the `GET /allocation_candidates API` ignored the aggregates on the nested providers. This could result in the lack of allocation candidates when an aggregate is on a nested provider but the aggregate is not on its root provider and the aggregate is specified in the API by the `member_of` query parameter. This patch fixes the bug changing it to consider the aggregates not only on root rps but also on the nested rp itself and adds a release note for this. The document which explains the whole constraint of `member_of` and other query parameters with nested providers, will be submitted in a follow up patch. Change-Id: I9a11a577174f85a1b47a9e895bb25cadd90bd2ea Closes-Bug: #1792503
12 lines
484 B
YAML
12 lines
484 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Previously, when an aggregate was specified by the ``member_of``
|
|
query parameter in the ``GET /allocation_candidates`` operation,
|
|
the non-root providers in the aggregate were excluded unless their
|
|
root provider was also in the aggregate. With this release, the
|
|
non-root providers directly associated with the aggregate are also
|
|
considered. See the `Bug#1792503`_ for details.
|
|
|
|
.. _Bug#1792503: https://bugs.launchpad.net/nova/+bug/1792503
|