Bug 1211976

Summary:	[New] - Creating a brick with out providing the brick names gives "Internal Engine error"
Product:	[Retired] oVirt	Reporter:	RamaKasturi <knarra>
Component:	ovirt-engine-webadmin	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Stanislav Graf <sgraf>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.6	CC:	bugs, dpati, ecohen, gklein, lsurette, mgoldboi, rbalakri, rnachimu, yeylon
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	gluster
Fixed In Version:	ovirt-engine-3.6.0-0.0.master.20150505172359.gitd1a6d14.el6.noarch.rpm	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 11:17:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1187461

Description RamaKasturi 2015-04-15 10:38:49 UTC

Description of problem:
When user tries to create a brick with out giving a name to the brick, it says Internal Engine error.

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add a rhel7 node to the cluster.
2. Sync all the storage devices 
3. Now select a device and click on create brick.
4. with out providing the name click "OK".

Actual results:
Engine displays operation cancelled with  "Internal  engine error " and an event message is displayed saying "Failed to create brick <UNKNOWN>"

Expected results:
UI should display a message saying "brick name is not given"

Additional info:

Comment 1 RamaKasturi 2015-05-19 06:47:09 UTC

Verified and works fine with build ovirt-engine-3.6.0-0.0.master.20150517172245.git089e126.el6.noarch.

when user tries creating a brick name with out brick name, the brick name text box is high lighted in red.

Comment 2 Sandro Bonazzola 2015-11-04 11:17:55 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.