alarm_id cannot be queried with /v2/query/alarms API with SQL backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Medium
|
Balazs Gibizer |
Bug Description
With SqlAlchemy backend the following exception is thrown if alarm_id is inculded in the filter on the /v2/query/alarms API
2014-02-20 17:19:04.822 6305 ERROR wsme.api [-] Server-side error: "type object 'Alarm' has no attribute 'alarm_id'". Detail:
Traceback (most recent call last):
File "/usr/local/
result = f(self, *args, **kwargs)
File "/opt/stack/
query.limit)]
File "/opt/stack/
return self._retrieve_
File "/opt/stack/
transformer
File "/opt/stack/
condition = self._transform
File "/opt/stack/
return self._handle_
File "/opt/stack/
return op(getattr(
AttributeError: type object 'Alarm' has no attribute 'alarm_id'
controller.lan - - [20/Feb/2014 17:19:04] "POST /v2/query/alarms HTTP/1.1" 500 127
This bug does not affect the Mongo DB backend.
Changed in ceilometer: | |
assignee: | nobody → Balazs Gibizer (balazs-gibizer) |
Changed in ceilometer: | |
milestone: | none → icehouse-rc1 |
importance: | Undecided → Medium |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | icehouse-rc1 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/75116
Review: https:/