Default alarm description not updated on threshold / meter change

[Leandro Ignacio Costantino]

Creating an alarm without description, and later on updating threshold / meter won't update (change) the output default description. This can be really confusing for end users.

Sample
-------------

+---------------------------+----------------------------------------------------------------------+
| Property | Value |
+---------------------------+----------------------------------------------------------------------+
| alarm_actions | [u'http://localhost:12000/'] |
| alarm_id | 7c1324d2-a96b-4f6f-af52-c05ea33fd866 |
| comparison_operator | lt |
| description | Alarm when network.outgoing.bytes is lt a avg of 33.0 over 5 seconds |
| enabled | True |
| evaluation_periods | 1 |
| exclude_outliers | False |
| insufficient_data_actions | [u'http://localhost:12000/'] |
| meter_name | new |
| name | bytes |
| ok_actions | [u'http://localhost:12000/'] |
| period | 100 |
| project_id | c8d29398c19846b2b7b7175a8acf73c9 |
| query | |
| repeat_actions | True |
| state | insufficient data |
| statistic | avg |
| threshold | 33.0 |
| type | threshold |
| user_id | 79816b624879417fa12dd7ecdc395a0e |
+---------------------------+----------------------------------------------------------------------+
ubuntu@ubuntu-SVT13125CLS:/opt/stack/ceilometer/ceilometer/api$ ceilometer alarm-threshold-update -a 7c1324d2-a96b-4f6f-af52-c05ea33fd866 -m new --threshold 500
+---------------------------+----------------------------------------------------------------------+
| Property | Value |
+---------------------------+----------------------------------------------------------------------+
| alarm_actions | [u'http://localhost:12000/'] |
| alarm_id | 7c1324d2-a96b-4f6f-af52-c05ea33fd866 |
| comparison_operator | lt |
| description | Alarm when network.outgoing.bytes is lt a avg of 33.0 over 5 seconds |
| enabled | True |
| evaluation_periods | 1 |
| exclude_outliers | False |
| insufficient_data_actions | [u'http://localhost:12000/'] |
| meter_name | new |
| name | bytes |
| ok_actions | [u'http://localhost:12000/'] |
| period | 100 |
| project_id | c8d29398c19846b2b7b7175a8acf73c9 |
| query | |
| repeat_actions | True |
| state | insufficient data |
| statistic | avg |
| threshold | 500.0 |
| type | threshold |
| user_id | 79816b624879417fa12dd7ecdc395a0e |
+---------------------------+----------------------------------------------------------------------+

[ZhiQiang Fan (aji-zqfan)]

so if we call rest api, we need to provide the description explicitly, otherwise it will be set to default generated description, I think this problem exists in python-ceilometerclient side

[ZhiQiang Fan (aji-zqfan)]

although I have a solution to fix this problem, but maybe we can treat it as not a bug but an user guide problem, for i.e., if we want to use default description while we modify the related field, then, specifiy--description '' will solve this problem. Or if we don't certain if a field will affect the default description, then we can always specify --description '' as long as we want to use the default description

[Pooja Tiwari (pooja-tiwari)]

I have succesfully reproduced this bug and have completed analysis to fix this issue.I will commit the changes shortly.Thanks.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/97777

[Pooja Tiwari (pooja-tiwari)]

I have proposed fix for this bug and submitted various patches as per review comments. I was facing issues in unit test execution for ceilometer, due this i was not able to add a unit thest case for this bug. Therefore i am unassigning this big.
Please go ahead and fix it. If possible please let me know how to execute unit test cases of ceilometer.

[OpenStack Infra (hudson-openstack)]

Change abandoned by gordon chung (<email address hidden>) on branch: master
Review: https://review.openstack.org/97777
Reason: inactive, please reopen if important.