Bug 994904
| Summary: | Edit dialog for alert conditions loads condition parameters incorrectly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Filip Brychta <fbrychta> | ||||
| Component: | Alerts, Core UI | Assignee: | Jirka Kremser <jkremser> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.8 | CC: | hrupp, jkremser | ||||
| Target Milestone: | --- | ||||||
| Target Release: | RHQ 4.10 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-04-23 12:30:24 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: | 973140 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Covered by automation - com.redhat.qe.jon.sahi.tests.alerts.AlertDefinitioinTest Works in master, it was probably fixed by commit 9c2e41ff Verified on Version : 4.10.0-SNAPSHOT Build Number : afc0857 Moving it back to ON_DEV. The issue is still there for some combinations. Use following conditions: - Metric Value Baseline [Up Time < 12.0 % of max] - Metric Value Threshold [Number of Commands Sent but Failed = 12.0] - Metric Value Range: [Number of Agent Restarts] outside [12.0] and [20.0], exclusive - Metric Value Change [Number of Commands Received but Failed per Minute] branch: master link: http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=8b14a1f9c time: 2014-01-06 18:13:19 +0100 commit: 8b14a1f9c08d9f40fd3692e1c2da5a977ce8b57d author: Jirka Kremser - jkremser message: [BZ 994904] - Edit dialog for alert conditions loads condition parameters incorrectly - The metric name was filtered out as a reaction on BZ 737565. Although, it does make sense to do that for all _other_ conditions, it does not make sense to filter out the metric name of the currently modified condition. (the original bug was fixed before the UI was capable of editing existing alert conditions). btw. only these two conditions were necessary for reproduction (on RHQ Agent resource): - Metric Value Threshold [Number of Commands Sent but Failed = 12.0] - Metric Value Range: [Number of Agent Restarts] outside [12.0] and [20.0] Verified on: 4.10.0-SNAPSHOT Build Number : 5450097 Bulk closing of 4.10 issues. If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10. |
Created attachment 784254 [details] alert condition Description of problem: When editing alert condition of 'Measurement Absolute Value Threshold' type, a 'Metric' field is filled incorrectly. See attached screen shot. There is a number (id of metric probably) instead of name of the metric. Version-Release number of selected component (if applicable): Version: 4.9.0-SNAPSHOT Build Number: ee56897 How reproducible: Always Steps to Reproduce: 1. create alert definition and add condition of type 'Measurement Absolute Value Threshold' (i.e. on RHQ agent resource) 2. select some metric, comparator, put a value 3. Save the condition 4. select the condition and pop up edit dialog Actual results: see attached screen shot Expected results: correct metric name is displayed Additional info: the same problem affects 'Measurement Baseline Threshold', 'Measurement Value Change', 'Measurement Value Range' types