Bug 987959 - Inconsistency between error tooltip and error dialog in Network QoS dialog
Summary: Inconsistency between error tooltip and error dialog in Network QoS dialog
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3
Assignee: Doron Fediuck
QA Contact:
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 13:17 UTC by Assaf Muller
Modified: 2013-09-23 07:34 UTC (History)
5 users (show)

Fixed In Version: IS9
Clone Of:
Environment:
Last Closed: 2013-09-23 07:34:35 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 17369 0 None None None Never

Description Assaf Muller 2013-07-24 13:17:21 UTC
Description of problem:
In the 'New Network QoS' dialog, the error tooltips say that the permitted values are between -2B and +2B, but if you enter a negative value an error dialog pops up and says that the value is invalid.

Version-Release number of selected component (if applicable):
http://pastebin.test.redhat.com/154829

How reproducible:
100%

Steps to Reproduce:
1. Click on Data Centers
2. Select a data center
3. Click on the Network QoS subtab
4. Click on new
5. Fill in all fields properly, but input a single QoS field with a letter and not a number
6. Click OK
7. Hover over the bad field. The tooltip will display: "This field must contain integer number between -2147483648 and 2147483647"
8. If you then input a negative number instead of a letter, an error dialog pops up with: "Error while executing action: Cannot add Network QoS. Values are out of range."


Actual results:
The tooltip doesn't sync up with the error dialog

Expected results:
The tooltip should not suggest that negative values are permitted

Comment 2 Itamar Heim 2013-09-23 07:34:35 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)


Note You need to log in before you can comment on or make changes to this bug.