Time constraint value does not display properly on the return table.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-ceilometerclient |
Fix Released
|
Medium
|
Rohit Jaiswal |
Bug Description
Create a new alarm or Update an existing alarm, and set time constraint, the time constraint value is truncated and displays on wrong page.
root@linuxuser:
+------
| Property | Value |
+------
| | |
| | duration: 10800, |
| | description: test, |
| | start: 0 18 * * *, |
| | timezone: US/Pacific}] |
| alarm_actions | [] |
| alarm_id | ac640d32-
| comparison_operator | eq |
| description | Alarm when meter1 is eq a avg of 1.0 over 60 seconds |
| enabled | True |
| evaluation_periods | 1 |
| exclude_outliers | False |
| insufficient_
| meter_name | meter1 |
| name | alarm1 |
| ok_actions | [] |
| period | 60 |
| project_id | |
| query | |
| repeat_actions | False |
| state | insufficient data |
| statistic | avg |
| threshold | 1.0 |
| time_constraints | [{name: sampleconstraint, |
| type | threshold |
| user_id | cde29f66655b4d6
+------
Changed in python-ceilometerclient: | |
assignee: | nobody → Rohit Jaiswal (rohit-jaiswal-3) |
status: | New → Incomplete |
status: | Incomplete → In Progress |
Changed in python-ceilometerclient: | |
importance: | Undecided → Medium |
Changed in python-ceilometerclient: | |
milestone: | none → 1.3.0 |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/136546
Review: https:/