Blazar

Tempest test fails during create_lease when before_end_lease data < start_date

Bug #1326523 reported by Pablo Andres Fuente
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Blazar
Fix Released
High
Pablo Andres Fuente
Blazar 0.1.1

Bug Description

Our Tempest test fails when tries to create a lease with a before_end_lease date less than lease start_date. This happens because the lease don't have an id yet and that property is used in a log line.

https://github.com/stackforge/blazar/blob/master/climate/manager/service.py#L452

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/97929

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

Reviewed: https://review.openstack.org/97929
Committed: https://git.openstack.org/cgit/stackforge/blazar/commit/?id=311708b2caa4a1b4fa8cd9770941d9c50d512fa1
Submitter: Jenkins
Branch: master

commit 311708b2caa4a1b4fa8cd9770941d9c50d512fa1
Author: Pablo Andres Fuente <email address hidden>
Date: Wed Jun 4 17:46:27 2014 -0300

    Made lease id optional in create_lease logging

    Fixed a crash that happened when a user tried to create a lease with a
    before_end_lease date sooner than the start_date date.
    When this situation happened a log line crashed because it was trying
    to access the lease id, which was not defined at that moment.

    Change-Id: I846761eb447d18892d0ad8910df22784d73b2bf9
    Closes-Bug: #1326523

Changed in blazar:
status: In Progress → Fix Committed
Masahito Muroi (muroi-masahito)
Changed in blazar:
milestone: none → 0.1.1
Masahito Muroi (muroi-masahito)
Changed in blazar:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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