Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1219372 - Info about 'severity' field changes is not displayed via alarm-history call
Info about 'severity' field changes is not displayed via alarm-history call
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ceilometer (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
unspecified Severity unspecified
: beta
: 8.0 (Liberty)
Assigned To: Eoghan Glynn
Yurii Prokulevych
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-05-07 04:01 EDT by Yurii Prokulevych
Modified: 2016-04-07 17:01 EDT (History)
5 users (show)

See Also:
Fixed In Version: openstack-ceilometer-5.0.0-1.el7ost
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-07 17:01:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1452264 None None None Never
Red Hat Product Errata RHEA-2016:0603 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 Enhancement Advisory 2016-04-07 20:53:53 EDT

  None (edit)
Description Yurii Prokulevych 2015-05-07 04:01:55 EDT
Description of problem:


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

rpm -qa | grep ceilo
openstack-ceilometer-common-2015.1.0-1.el7.noarch
openstack-ceilometer-alarm-2015.1.0-1.el7.noarch
openstack-ceilometer-compute-2015.1.0-1.el7.noarch
openstack-ceilometer-collector-2015.1.0-1.el7.noarch
openstack-ceilometer-notification-2015.1.0-1.el7.noarch
openstack-ceilometer-central-2015.1.0-1.el7.noarch
python-ceilometerclient-1.0.13-1.el7.noarch
openstack-ceilometer-api-2015.1.0-1.el7.noarch
python-ceilometer-2015.1.0-1.el7.noarch

Steps to Reproduce:


Changes to the alarm's severity are not displayed in 'ceilometer alarm-history <alarm_id> ' output:

# ceilometer alarm-history 357ce1eb-839e-4782-8676-11a7b7ef5d18
+------------------+---------------------+----------------------------------------------------+
| Type | Timestamp | Detail |
+------------------+---------------------+----------------------------------------------------+
| state transition | 2015-05-06T09:53:37 | state: insufficient data |
| state transition | 2015-05-06T09:50:37 | state: alarm |
| state transition | 2015-05-06T09:20:36 | state: ok |
| rule change | 2015-05-06T09:14:38 | enabled: True |
| rule change | 2015-05-06T07:48:13 | enabled: False |
| creation | 2015-05-06T05:56:40 | name: ThresholdAlarm-1-moderate |
| | | description: Test Alarm TC474397 moderate |
| | | type: threshold |
| | | rule: alarm_meter_1_moderate >= 3.0 during 3 x 60s |
| | | time_constraints: None |
+------------------+---------------------+----------------------------------------------------+

# ceilometer alarm-threshold-update 357ce1eb-839e-4782-8676-11a7b7ef5d18 --severity low >/dev/null 2>&1

# ceilometer alarm-history 357ce1eb-839e-4782-8676-11a7b7ef5d18
+------------------+----------------------------+----------------------------------------------------+
| Type | Timestamp | Detail |
+------------------+----------------------------+----------------------------------------------------+
| rule change | 2015-05-06T11:57:32.345000 | |
| state transition | 2015-05-06T09:53:37.125000 | state: insufficient data |
| state transition | 2015-05-06T09:50:37.021000 | state: alarm |
| state transition | 2015-05-06T09:20:36.895000 | state: ok |
| rule change | 2015-05-06T09:14:38.644000 | enabled: True |
| rule change | 2015-05-06T07:48:13.844000 | enabled: False |
| creation | 2015-05-06T05:56:40.562000 | name: ThresholdAlarm-1-moderate |
| | | description: Test Alarm TC474397 moderate |
| | | type: threshold |
| | | rule: alarm_meter_1_moderate >= 3.0 during 3 x 60s |
| | | time_constraints: None |
+------------------+----------------------------+----------------------------------------------------+

# ceilometer alarm-threshold-update 357ce1eb-839e-4782-8676-11a7b7ef5d18 --severity critical >/dev/null 2>&1

# ceilometer alarm-history 357ce1eb-839e-4782-8676-11a7b7ef5d18
+------------------+----------------------------+----------------------------------------------------+
| Type | Timestamp | Detail |
+------------------+----------------------------+----------------------------------------------------+
| rule change | 2015-05-06T11:58:47.653000 | |
| rule change | 2015-05-06T11:57:32.345000 | |
| state transition | 2015-05-06T09:53:37.125000 | state: insufficient data |
| state transition | 2015-05-06T09:50:37.021000 | state: alarm |
| state transition | 2015-05-06T09:20:36.895000 | state: ok |
| rule change | 2015-05-06T09:14:38.644000 | enabled: True |
| rule change | 2015-05-06T07:48:13.844000 | enabled: False |
| creation | 2015-05-06T05:56:40.562000 | name: ThresholdAlarm-1-moderate |
| | | description: Test Alarm TC474397 moderate |
| | | type: threshold |
| | | rule: alarm_meter_1_moderate >= 3.0 during 3 x 60s |
| | | time_constraints: None |
+------------------+----------------------------+----------------------------------------------------+

Expected results:

Info about alarm's severity change is displayed
Comment 1 Pradeep Kilambi 2015-12-04 12:06:48 EST
This is fixed in liberty, i would move it to on_qa.
Comment 2 Yurii Prokulevych 2015-12-07 07:41:24 EST
Packages:
rpm -qa | grep ceilo
openstack-ceilometer-api-5.0.0-2.el7ost.noarch
openstack-ceilometer-collector-5.0.0-2.el7ost.noarch
openstack-ceilometer-common-5.0.0-2.el7ost.noarch
openstack-ceilometer-compute-5.0.0-2.el7ost.noarch
openstack-ceilometer-polling-5.0.0-2.el7ost.noarch
openstack-ceilometer-central-5.0.0-2.el7ost.noarch
openstack-ceilometer-notification-5.0.0-2.el7ost.noarch
python-ceilometerclient-1.5.0-1.el7ost.noarch
python-ceilometer-5.0.0-2.el7ost.noarch
openstack-ceilometer-alarm-5.0.0-2.el7ost.noarch
Comment 4 errata-xmlrpc 2016-04-07 17:01:17 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0603.html

Note You need to log in before you can comment on or make changes to this bug.