ceilometer alarm-threshold-update returns programming error message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-ceilometerclient |
Fix Released
|
Undecided
|
Eric Pendergrass |
Bug Description
Updating an alarm state via ceilometer client's alarm-threshold
ceilometer alarm-threshold
WARNING (http:173) Request returned failure status.
'NoneType' object has no attribute 'to_dict'
This is a PUT request. On contrary a similar alarm put request to change the alarm state returns a message that the alarm can't be found, which is more expected:
ceilometer alarm-state-set -a f4731698-
WARNING (http:173) Request returned failure status.
Alarm not found: f4731698-
Both commands run fine as admin user and tenant, so there is no problem with syntax or existence of the alarm id.
I would expect the first command to return the same message as the second, that the alarm isn't found (since the user/tenant pair isn't authorized to access it).
Furthermore the error appears to be an uncaught programming error since it references a failed attempted lookup on an object that was expected to be non-None.
Finally, the problem error message is printed for a bogus alarm id as well, and this doesn't seem quite right.
affects: | ceilometer → python-ceilometerclient |
Changed in python-ceilometerclient: | |
status: | In Progress → Fix Committed |
Changed in python-ceilometerclient: | |
milestone: | none → 1.3.0 |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/110343
Review: https:/