Bug 1254381

Summary:	A pool name can be set as empty
Product:	[Retired] Beaker	Reporter:	matt jia <mjia>
Component:	web UI	Assignee:	Roman Joost <rjoost>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	dcallagh, dowang, mjia, rjoost
Target Milestone:	21.1	Keywords:	NeedsTestCase, Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-21 03:25:20 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 matt jia 2015-08-17 22:35:29 UTC

Description of problem:

A pool name can be updated with empty value.

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. go to a pool edit page
2. click Edit button
3. change name to empty and Click on Save Changes button

Actual results:

The pool's name is set as empty

Expected results:

Should not allow to set name as empty

Comment 1 Dan Callaghan 2015-08-24 04:45:58 UTC

Should be able to just add a SQLAlchemy validator to ensure the name is not empty string.

Comment 2 Roman Joost 2015-08-24 23:01:42 UTC

Patch in Gerrit:

https://gerrit.beaker-project.org/#/c/4364/

Comment 5 Dan Callaghan 2015-10-21 03:25:20 UTC

Beaker 21.1 has been released.