multiple host aggregates of host failure
Bug #1856164 reported by
Toshikazu Ichikawa
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| masakari |
Fix Released
|
Medium
|
Daisuke Suzuki | ||
| Train |
Fix Committed
|
Undecided
|
Unassigned | ||
| Ussuri |
Fix Committed
|
Undecided
|
Unassigned | ||
| Victoria |
Fix Committed
|
Undecided
|
Unassigned | ||
| Wallaby |
Fix Released
|
Medium
|
Daisuke Suzuki | ||
Bug Description
In real production, a failed host and a reserved host may have multiple host aggregates because operators need to control the provisioning based on several guest OS and instance flavors.
Current implementation only adds a reserved_host to the very first aggregate from the list of a failed compute host, as noted in host_failure.py.
This limitation needs to be removed.
| Changed in masakari: | |
| status: | New → Confirmed |
| Changed in masakari: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Daisuke Suzuki (suzuki-di) |
To post a comment you must log in.
This is addressed by https:/ /review. opendev. org/c/openstack /masakari/ +/772829