d564266a01
If a host is specified during an evacuate with the force=True flag, conductor bypasses the scheduler. Since the scheduler is what creates the "doubled up" allocation on the destination node, and the scheduler is bypassed in the force case, we have to create the allocations against the destination node in conductor directly. The unit tests cover the failure scenarios. The functional test covers the happy path. This is a short-term backportable fix. Long-term we'll likely want to call the scheduler even in the 'force' scenario but pass a flag to the scheduler to tell it to skip the filters but still create the allocation on the destination node so we don't have to duplicate that in conductor. Change-Id: I6590f0eda4ec4996543ad40d8c2640b83fc3dd9d Partial-Bug: #1713786
12 lines
546 B
YAML
12 lines
546 B
YAML
---
|
|
fixes:
|
|
- |
|
|
When forcing a specified destination host during evacuate, the
|
|
scheduler is bypassed but resource allocations will still be made in the
|
|
Placement service against the forced destination host. If the resource
|
|
allocation against the destination host fails, the evacuate operation
|
|
will fail, regardless of the ``force`` flag being specified in the API.
|
|
The guest will be unchanged on the source host. For more details, see
|
|
`bug 1713786`_.
|
|
|
|
.. _bug 1713786: https://bugs.launchpad.net/nova/+bug/1713786 |