Querying alarm history using severity field breaks the API
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Aodh |
Fix Released
|
Undecided
|
Rohit Jaiswal | ||
Ceilometer |
Opinion
|
Medium
|
Rohit Jaiswal |
Bug Description
I've been working on delivering unittests for oslo.versionedo
Here is my sample request:
http://
Which gives me 500 response:
{
"error_
}
}
+ Traceback:
2015-07-09 14:22:09.815 22333 ERROR wsme.api [-] Server-side error: "type object 'AlarmChange' has no attribute 'severity'". Detail:
Traceback (most recent call last):
File "/usr/local/
result = f(self, *args, **kwargs)
File "/opt/stack/
**kwargs)]
File "/opt/stack/
query = query.filter(
AttributeError: type object 'AlarmChange' has no attribute 'severity'
Indeed AlarmChange model does not have a field severity (it's only on the Alarm model), so the exception message is pretty obvious.
Changed in ceilometer: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in ceilometer: | |
assignee: | nobody → Rohit Jaiswal (rohit-jaiswal-3) |
Changed in aodh: | |
assignee: | nobody → Rohit Jaiswal (rohit-jaiswal-3) |
Changed in ceilometer: | |
status: | In Progress → Opinion |
Changed in aodh: | |
assignee: | Rohit Jaiswal (rohit-jaiswal-3) → Chris Dent (chdent) |
Changed in aodh: | |
assignee: | Chris Dent (chdent) → Rohit Jaiswal (rohit-jaiswal-3) |
Changed in aodh: | |
milestone: | none → 1.0.0 |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/200238
Review: https:/