multiple host aggregates of host failure

Bug #1856164 reported by Toshikazu Ichikawa
6
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)
Revision history for this message
Radosław Piliszek (yoctozepto) wrote :
Changed in masakari:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/masakari 11.0.0.0rc1

This issue was fixed in the openstack/masakari 11.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/masakari 8.1.2

This issue was fixed in the openstack/masakari 8.1.2 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/masakari 9.1.2

This issue was fixed in the openstack/masakari 9.1.2 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/masakari 10.0.2

This issue was fixed in the openstack/masakari 10.0.2 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.