Red Hat Bugzilla – Bug 535806
Alert definition creation doesn't reject invalid number format
Last modified: 2014-11-09 17:49:47 EST
Create an alert def, on the "Absolute Value" or "% of" number fields, enter a number formatted like this: "1.2.3" or "99.9.9". Fill out the rest of the alert fields and click ok. Instead of rejecting the bad input, it accepts it, but truncates from the 2nd dot.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2464
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.
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.
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
botched this verify..
adding 99.9.9 to abs value to a measurement threshold.
try strings.. "asdf"
now trying w/
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..
is > x
enter in 126.96.36.199
The value is truncated to 1.2 after submit.
188.8.131.52 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
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...
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.