Bug 987959 - Inconsistency between error tooltip and error dialog in Network QoS dialog
Inconsistency between error tooltip and error dialog in Network QoS dialog
Product: oVirt
Classification: Community
Component: ovirt-engine-webadmin (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.3
Assigned To: Doron Fediuck
Depends On:
  Show dependency treegraph
Reported: 2013-07-24 09:17 EDT by Assaf Muller
Modified: 2013-09-23 03:34 EDT (History)
5 users (show)

See Also:
Fixed In Version: IS9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-23 03:34:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 17369 None None None Never

  None (edit)
Description Assaf Muller 2013-07-24 09:17:21 EDT
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):

How reproducible:

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 03:34:35 EDT
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.