Null time constraint in alarm creation raises an error

Bug #1427234 reported by Julien Danjou
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Fix Released
High
Julien Danjou

Bug Description

If an alarm is created with a time constrait set to null, the server returns an error 500.

Julien Danjou (jdanjou)
Changed in ceilometer:
importance: Undecided → High
status: New → In Progress
assignee: nobody → Julien Danjou (jdanjou)
Revision history for this message
Julien Danjou (jdanjou) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ceilometer (master)

Reviewed: https://review.openstack.org/155819
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=1db748a8e102da6fc79883ef0ed3f164339719b1
Submitter: Jenkins
Branch: master

commit 1db748a8e102da6fc79883ef0ed3f164339719b1
Author: Julien Danjou <email address hidden>
Date: Fri Feb 13 17:57:48 2015 +0100

    api: fix alarm creation if time_constraint is null

    Closes-Bug: #1427234

    Change-Id: I31b16f404e5b60545957d554be4e933c0312210e

Changed in ceilometer:
status: In Progress → Fix Committed
gordon chung (chungg)
Changed in ceilometer:
milestone: none → kilo-3
Thierry Carrez (ttx)
Changed in ceilometer:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in ceilometer:
milestone: kilo-3 → 2015.1.0
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.