Bug 1016502

Summary: No warning pop-up when set data size beginning with "-1*"
Product: Red Hat Enterprise Linux 6 Reporter: cshao <cshao>
Component: ovirt-nodeAssignee: Ryan Barry <rbarry>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: acathrow, bsarathy, cboyle, cpelland, fdeutsch, gouyang, hadong, huiwa, jboggs, leiwang, mburns, ovirt-maint, tlavigne, yaniwang, ycui
Target Milestone: rcKeywords: TestOnly
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.0.1-14.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 19:53:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
data
none
error none

Description cshao 2013-10-08 09:43:40 UTC
Created attachment 809188 [details]
data

Description of problem:
No warning pop-up when set data size beginning with "-1*", and an exception has occurred.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20131003.0.el6_4
ovirt-node-2.5.0-17.el6_4.9.noarch 

How reproducible:
100%

Steps to Reproduce:
1. Boot from PXE.
2. TUI install RHEV-H
3. Set data size beginning with "-1*" (e.g. -111)

Actual results:
RHEV-H install failed and an exception has occurred.

Expected results:
Pop-up warning msg when set data size beginning with "-1*".

Additional info:

Comment 1 cshao 2013-10-08 09:44:27 UTC
Created attachment 809189 [details]
error

Comment 3 Fabian Deutsch 2013-10-08 12:46:22 UTC
This is probably fixed in the new UI shipping in 6.5, thus TestOnly.

Comment 6 Charlie 2014-01-15 05:37:43 UTC
Does this need doctext? I'm suspecting not. Thanks.

Comment 7 Ryan Barry 2014-01-15 15:25:34 UTC
Doesn't need doctext.

Comment 9 errata-xmlrpc 2014-01-21 19:53:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0033.html