Bug 1008426

Summary:	Input error not shown in edit VM/Template dialog when advanced options are hidden
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	tgeft
Component:	ovirt-engine-webadmin-portal	Assignee:	Tomas Jelinek <tjelinek>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, ecohen, iheim, michal.skrivanek, nobody, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-10 07:09:05 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:
Embargoed:

Description tgeft 2013-09-16 10:57:43 UTC

Description of problem:
If one of the fields in the advanced options (System, initial run, ...) of the VM/template dialog is incorrect and the user has hidden the advanced options, the error will not be visible to the user when clicking OK. To see the problematic field, the user will have to click "Show Advanced Options". 


Version-Release number of selected component (if applicable):
3.3.0-0.21.master.el6ev

How reproducible:
100%

Steps to Reproduce:

Simple artificial scenario:
1. Enter the new VM dialog, open the advanced options, and input 0 in the 'Total Virtual CPUs' field (under 'System').
2. Hide the advanced options and click OK

More realistic scenario:
1. Edit a VM to run on host X in the host placement option (choose "specific" -> host X) and click OK.
2. Move the host to another DC.
3. Try to edit the VM's name and click OK. (without expanding the advanced options)

Actual results:
In both cases clicking OK will result in no apparent action nor error. The user will have to look at the advanced options to find the problematic field.

Expected results:
The advanced options should expand automatically to allow the user to see the error. Alternatively, bring up an error dialog about the problematic field.


Additional info:

Comment 2 Tomas Jelinek 2014-04-10 07:09:05 UTC


*** This bug has been marked as a duplicate of bug 1085380 ***