Bug 535806 (RHQ-2464)
| Summary: | Alert definition creation doesn't reject invalid number format | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Jeff Weiss <jweiss> |
| Component: | Alerts | Assignee: | John Mazzitelli <mazz> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.3 | CC: | cwelton, dajohnso, whayutin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://jira.rhq-project.org/browse/RHQ-2464 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-02 07:23:08 UTC | Type: | --- |
| 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: | 547833, 562434, 565632, 585306, 591531 | ||
|
Description
Jeff Weiss
2009-10-14 18:54:00 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2464 Sachin, There may be several field checking issues regarding Alerts, I have found a few as well. Can you drive this bug, and look for other similar issues. Thanks I will assign out when it is updated. Sorry, I may have been unclear. The bug is what is described in the description. It is ready to be assigned to a developer. Sachin will be the QA contact. Thanks I am able to create Alert Name with spl char ie : ****************** which should not be allowed . Alert if Condition absolute Value option accepts -ve value ie : -0.1B which should not be allowed mass move to rhq_chainsaw tracker bug This bug has now been triaged by Chainsaw on 2/18. The expectation is the bug to be addressed by the end of sprint06 roughly 3/10/10. In commit: dbbfa75ddfa4ce4443f2f72df49b483970ea4e8c using names for alerts like 1.2.3 and 99.9% seem to be valid now and the links work verified botched this verify.. retesting.. adding 99.9.9 to abs value to a measurement threshold. pass try strings.. "asdf" pass now trying w/ Measurement Baseline any metric is > x enter in 10.8888888888 The value is truncated to 10.9 after submit. So as the bug is written this fails. passing back to jharris to either fix or close as working as designed. sorry.. and to add.. Measurement Baseline any metric is > x enter in 1.2.3.4 The value is truncated to 1.2 after submit. 1.2.3.4 should be rejected as invalid.. Reassigning because I'm pretty sure Justin is no longer the dev for this component. will look to see about putting in validators on the fields commit f211290 The following fields now have validators on them: Measurement Absolute Value Threshold : Metric Value Measurement Baseline Threshold : Baseline Percentage Call Time Value Threshold : Call Time Value Call Time Value Change : Percentage Change You now must enter a valid decimal. NOTE: you do not enter the percentage values as decimals (i.e. you do not enter .4 to mean 40%, you explicitly enter "40" to represent 40%) but you can enter fractional percentages (i.e. you enter "40.5" to represent 40.5%). verified as follows: tested numeric fields with invalid numeric values... 9.9 valid 9.9.9 invalid 0.1 valid 0.1B invalid abc invalid #111 invalid Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago. |