Bug 1551105

Summary: webadmin exception in New Virtual Disk dialog when disk size field validation fails
Product: [oVirt] ovirt-engine Reporter: jniederm
Component: Frontend.WebAdminAssignee: Alexander Wels <awels>
Status: CLOSED CURRENTRELEASE QA Contact: samuel macko <smacko>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: awels, bugs, gshereme, lsvaty, lveyde, tjelinek
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:00:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
stacktrace.txt none

Description jniederm 2018-03-02 18:38:25 UTC
Created attachment 1403150 [details]
stacktrace.txt

Description of problem:
Vojtobox is shown when New Virtual Disk dialog contains invalid size (letter in the textbox) and Enter key is pressed

Version-Release number of selected component (if applicable):
current master, commit da07334df4

How reproducible:
100%

Steps to Reproduce:
1. create a VM
2. click the VM
3. select Disks page
4. click New toolbar button
5. type 'qwe' into size textbox
6. press enter key

Actual results:
Vojtobox shown

Expected results:
field is marked invalid (red highlighting), hint explains that positive integer is expected

Additional info:
workaround: click OK button

Comment 2 Alexander Wels 2018-03-13 17:15:36 UTC
Yes, but has happened already, see attached patches.

Comment 3 samuel macko 2018-03-19 14:05:53 UTC
Verified in ovirt version 4.2.2.4-0.1.el7.

Verified by following the reproducer.

Comment 4 Sandro Bonazzola 2018-03-29 11:00:25 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

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