Prevent leases from being deleted if they are not in the right state

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

Bug Description

A user can call DELETE on a lease while it is starting, for example, which will trigger an error condition (on_end will try to delete the corresponding aggregate). We must prevent users from calling delete if the lease is not in a state that allows it (e.g. PENDING or ACTIVE).

Pierre Riteau (priteau)
Changed in blazar:
importance: Undecided → High
assignee: nobody → Pierre Riteau (priteau)
milestone: none → stein-1
status: New → Confirmed
Pierre Riteau (priteau)
Changed in blazar:
milestone: stein-1 → stein-2
Pierre Riteau (priteau)
Changed in blazar:
milestone: stein-2 → stein-3
Pierre Riteau (priteau)
Changed in blazar:
status: Confirmed → In Progress
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/636700

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to blazar (master)

Reviewed: https://review.openstack.org/636700
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=00760ae25bc528c97769426b7a3914b91becf32a
Submitter: Zuul
Branch: master

commit 00760ae25bc528c97769426b7a3914b91becf32a
Author: Pierre Riteau <email address hidden>
Date: Mon Feb 18 17:50:54 2019 +0000

    Prevent leases from being deleted during event execution

    A user can request to delete a lease while it is changing state via
    event execution, which can trigger an error condition as on_end will
    attempt to delete the corresponding aggregate.

    This commit prevents a lease from being deleted while its start_lease or
    end_lease events are in progress.

    Change-Id: I73bde0219b6ea30d16564fd2507fd59d52cbfa6a
    Closes-Bug: #1791741

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.