Null time constraint in alarm creation raises an error
Bug #1427234 reported by
Julien Danjou
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.
Changed in ceilometer: | |
importance: | Undecided → High |
status: | New → In Progress |
assignee: | nobody → Julien Danjou (jdanjou) |
Changed in ceilometer: | |
milestone: | none → kilo-3 |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
review at https:/ /review. openstack. org/#/c/ 155819/