Hosts are not added to aggregate when updating an active reservation

Bug #1800463 reported by Pierre Riteau
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Fix Released
Critical
Pierre Riteau

Bug Description

When updating an active reservation, new hosts allocations are created but the Nova hosts are not added to the corresponding host aggregate. This prevents users from deploying instances on the newly allocated hosts.

Pierre Riteau (priteau)
Changed in blazar:
status: New → Incomplete
status: Incomplete → Confirmed
importance: Undecided → Critical
assignee: nobody → Pierre Riteau (priteau)
milestone: none → stein-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to blazar (master)

Fix proposed to branch: master
Review: https://review.openstack.org/613939

Changed in blazar:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to blazar (master)

Reviewed: https://review.openstack.org/613939
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=6e412b7751fe7431e9ac4b1140afaf7f7365aa55
Submitter: Zuul
Branch: master

commit 6e412b7751fe7431e9ac4b1140afaf7f7365aa55
Author: Pierre Riteau <email address hidden>
Date: Mon Oct 29 14:14:44 2018 +0000

    Add new hosts to aggregate when updating an active reservation

    When an active reservation was updated to increase its number of
    reserved hosts, new hosts allocations were created in the database, but
    the corresponding Nova hosts were not added to the host aggregate. This
    prevented users from deploying instances on the newly allocated hosts.

    This patch ensures newly allocated hosts are added to the aggregate when
    an active reservation is updated.

    Change-Id: I11904934319665c9e75558928c87fc92d856325d
    Closes-Bug: #1800463

Changed in blazar:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/blazar 3.0.0.0rc1

This issue was fixed in the openstack/blazar 3.0.0.0rc1 release candidate.

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.