Bug 1182573 - Incorrect error message when hovering over custom cpu shares
Summary: Incorrect error message when hovering over custom cpu shares
Keywords:
Status: CLOSED DUPLICATE of bug 1168315
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.4.4
Hardware: x86_64
OS: All
medium
medium
Target Milestone: ---
: 3.5.1
Assignee: Dudi Maroshi
QA Contact: Shira Maximov
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-15 13:46 UTC by Lukas Svaty
Modified: 2016-02-10 20:18 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-04 14:59:41 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
not empty being empty and not being not empty (143.95 KB, image/png)
2015-01-15 13:47 UTC, Lukas Svaty 		no flags Details
View All

Description Lukas Svaty 2015-01-15 13:46:41 UTC 
Description of problem:
See attached screenshot. Not empty field is not empty.

Version-Release number of selected component (if applicable):
av14.1

How reproducible:
100%

Steps to Reproduce:
1. Edit custom cpu shares with 'foo'
2. See error message
3.

Actual results:
Field can't be empty.

Expected results:
Field can't contain other symbols than numbers.

Additional info:
Comment 1 Lukas Svaty 2015-01-15 13:47:18 UTC 
Created attachment 980502 [details]
not empty being empty and not being not empty
Comment 2 Dudi Maroshi 2015-02-02 08:33:15 UTC 
Error was reproduced and traced.
The defect is in class IntegerEntityModelTextBoxOnlyEditor
The validator  ToIntEntityModelParser is returning wrong message. 
Defect relevant to all instanced of IntegerEntityModelTextBoxOnlyEditor (17 instances).

In addition found respective relevant defects for instances of:
ShortEntityModelTextBoxOnlyEditor (2 instances)
LongEntityModelTextBoxEditor (2 instances)
DoubleEntityModelLabelEditor (2 instances)
Comment 3 Roy Golan 2015-02-04 14:59:41 UTC 

*** This bug has been marked as a duplicate of bug 1168315 ***
Note You need to log in before you can comment on or make changes to this bug.