Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1144424

Summary:	Data filled in creation VM are dismissed when too long VM name is set
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Vaclav Ehrlich <vehrlich>
Component:	ovirt-engine-userportal	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	ecohen, gklein, iheim, lsurette, ofrenkel, rbalakri, Rhev-m-bugs, tpelka, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-22 13:56:37 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 Vaclav Ehrlich 2014-09-19 11:00:45 UTC

Description of problem:
When saving/creating VM with name too long (more than 16 chars) all data filled by user are dismissed (pop up window is closed).
It seems it's only for Windows VM (tested when creating Windows 7 and Windows 8 VMs)

Version-Release number of selected component (if applicable):
rhevm-userportal-3.5.0-0.11.beta.el6ev.noarch.rpm


How reproducible:
Alway for Win VM

Steps to Reproduce:
1.Login into userportal
2.click on New VM (New Virtual Machine pop up window is shown)
3.Fill necessary data, choose Windows 7 in Operating system (General tab)
4.Fill VM name longer than 16 chars
5.Click to Ok to save VM

Actual results:
Pop up with error message is open and only Close button is shown. After closing pop up window all filled data are lost.

Expected results:
There is error message in New Virtual Machine pop up window, user can correct name and then save.

Additional info:
RHEL VM handle more than 16 chars.

Comment 1 Omer Frenkel 2014-09-22 13:56:37 UTC


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