9dea55bd64
Currently host maintenance strategy also migrate instances from maintenance node to watcher_disabled compute nodes. watcher_disabled compute nodes might be disabled for some other purpose by different strategy. If host maintenace use those compute nodes for migration, It might affect customer workloads. Host maintenance strategy should never touch disabled hosts unless the user specify a disable host as backup node. This cr drops the logic for using disabled compute node for maintenance. Host maintaince is already using nova schedular for migrating the instance, will use the same. If there is no available node, strategy will fail. Closes-Bug: #2109945 Change-Id: If9795fd06f684eb67d553405cebd8a30887c3997 Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
11 lines
470 B
YAML
11 lines
470 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Host maintenance strategy should migrate servers based on backup node if specified
|
|
or rely on nova scheduler. It was enabling disabled hosts with watcher_disabled
|
|
reason and migrating servers to those nodes. It can impact customer workload. Compute
|
|
nodes were disabled for a reason.
|
|
|
|
Host maintenance strategy is fixed now to support migrating servers only on backup
|
|
node or rely on nova scheduler if no backup node is provided.
|