Description of problem:

Generic (i.e. non-threshold-related) alarm attributes cannot be updated with the alarm-threshold-update command, for example:

  $ ceilometer --debug alarm-threshold-update -a $ALARM_ID --repeat-actions True
  INFO (connectionpool:176) Starting new HTTP connection (1): 192.168.122.73
  DEBUG (connectionpool:344) "POST /v2.0/tokens HTTP/1.1" 200 9905
  'threshold_rule'

The non-update is not properly reported, i.e. the failure is semi-silent.


Version-Release number of selected component (if applicable):

Version-Release number of selected component (if applicable):

python-ceilometerclient-1.0.6-1.el6ost.noarch


How reproducible:

100%


Steps to Reproduce:
1. Create a new alarm:

   $ ceilometer alarm-threshold-create --name cpu_high --description 'instance running hot'  \
   --meter-name cpu_util  --threshold 70.0 \
   --comparison-operator gt  --statistic avg \
   --period 600 --evaluation-periods 3 \
   --alarm-action 'log://' \
   --query resource_id=INSTANCE_ID --repeat-actions True

2. Attempt to update some generic alarm attribute:

  $ ceilometer alarm-threshold-update -a $ALARM_ID --repeat-actions False

3. Note the attribute is not updated:

  $ ceilometer alarm-threshold-show -a $ALARM_ID | grep repeat
  
   

Actual results:

Attempt to update alarm attribute fails semi-silently.


Expected results:

Alarm attribute should be updated.