Bug 1232163
| Summary: | Info about 'severity' field changes is not displayed via alarm-history call | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Yurii Prokulevych <yprokule> |
| Component: | openstack-ceilometer | Assignee: | Chris Dent <chdent> |
| Status: | CLOSED ERRATA | QA Contact: | Yurii Prokulevych <yprokule> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 (Kilo) | CC: | eglynn, jruzicka, mlopes, pbrady, rrosa, sclewis, yeylon |
| Target Milestone: | ga | ||
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-ceilometer-2015.1.0-4.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previous versions of 'alarm-history' did not give an indication of when the severity of a given alarm was changed (for example, from 'low' to 'critical'); instead a change was indicated without any detail given of what the change was.
This update addresses this issue with a code update that displays severity changes.
As a result, 'alarm-history' now displays severity changes in the output of alarm-history.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-05 13:27:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1189621 | ||
|
Description
Yurii Prokulevych
2015-06-16 08:12:17 UTC
Adding tracker of upstream backport. For reference upstream stable/kilo commit is 023cfd11f385dbbc3800622ea45a0111d304f8d6 Some jiggery pokery was required to get a successful build of the RPMs due to bad whitespace in previous patches. Find cdent if there are issues. found issues with the build and patch process associated with this, redoing. Okay, new build, hopefully on proper branch. For sake of adding information to the commonwheal: I was testing the latest puddle this morning for general ceilometer stuff and attempted to test if this feature was there. It took me a while to realize it was because I was doing it a bit wrong. I was: * creating an alarm * doing an alarm-history In that case no severity information is shown. In order to get a report of the severity it is necessary to do `ceilometer alarm-threshold-update caa233f0-e46d-4554-9a01-a60602ab24f0 --severity <some severity>` and then redo the history. And then you'll see the severity. It is a (different) bug that the creation summary does not include severity or is that expected? Verified for threshold and combination alarms: ceilometer alarm-history 2f5a75c2-6f01-4a1d-918d-d9fb4af7ed83 +-------------+----------------------------+------------------------------------------------------------------------------------------------------------+ | Type | Timestamp | Detail | +-------------+----------------------------+------------------------------------------------------------------------------------------------------------+ | rule change | 2015-06-24T12:06:31.928000 | severity: critical | | rule change | 2015-06-24T12:03:40.996000 | severity: moderate | | rule change | 2015-06-24T11:55:32.745000 | severity: low | | creation | 2015-06-24T11:54:01.628000 | name: JenkinsAutoCombinationAlarm-1435146818-or-low-moderate-critical | | | | description: Combination Alarm with or severity | | | | type: combination | | | | rule: combinated states (OR) of e94f1638-de12-4cbf-b57d-7b6948a8bfb2, f1758de8-37e4-4fe0-986d-3e85e79b978c | | | | time_constraints: None | +-------------+----------------------------+------------------------------------------------------------------------------------------------------------+ +-------------+----------------------------+--------------------------------------------------------------+ | Type | Timestamp | Detail | +-------------+----------------------------+--------------------------------------------------------------+ | rule change | 2015-06-24T11:50:23.326000 | severity: critical | | rule change | 2015-06-24T11:48:54.467000 | severity: moderate | | rule change | 2015-06-24T11:42:06.490000 | severity: low | | creation | 2015-06-24T11:41:58.147000 | name: JenkinsAutoAlarm-1435146116_moderate | | | | description: Test Alarm JenkinsAutoAlarm-1435146116_moderate | | | | type: threshold | | | | rule: alarm_meter_1 >= 3.0 during 3 x 60s | | | | time_constraints: None | +-------------+----------------------------+--------------------------------------------------------------+ 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://access.redhat.com/errata/RHEA-2015:1548 |