Bug 967799 - Beaker shows a 500 error when modifying group name to a name which already exists
Summary: Beaker shows a 500 error when modifying group name to a name which already ex...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: develop
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 0.13
Assignee: Amit Saha
QA Contact: Nick Coghlan
URL:
Whiteboard: UX
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-28 11:10 UTC by xjia
Modified: 2018-02-06 00:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-25 06:27:08 UTC
Embargoed:


Attachments (Terms of Use)

Description xjia 2013-05-28 11:10:27 UTC
Description of problem:
Create a group named group1, and create another group named group2. Then modify group2's name to group1, it will show 500 error.

Version-Release number of selected component (if applicable):
beaker-server-redhat-0.1.14-1.el6eng.noarch
beaker-server-0.12.1-1.git.133.6c74a92.el6.noarch

How reproducible:
Always.

Steps to Reproduce:
1.Create a group named group1.
2.Creage a group named group2
3.Mofidy group2, change its name to "group1"
4.Save it

Actual results:
500 Internal error

Expected results:
Show the name has already existed.

Additional info:

Comment 1 Nick Coghlan 2013-05-29 01:31:43 UTC
Actually bringing this one into scope for 0.13, since people *will* do this in production and it should give them a nice error.

Comment 2 Amit Saha 2013-06-02 11:37:34 UTC
On Gerrit: http://gerrit.beaker-project.org/#/c/2007/2

Comment 4 Nick Coghlan 2013-06-06 07:53:16 UTC
Confirmed this works as expected on the integration instance:

1. Attempted to rename an existing group to the name of another existing group
2. Received a notification that a group with that name already existed
3. Existing group was left unchanged

Comment 6 Amit Saha 2013-06-25 06:27:08 UTC
Beaker 0.13.1 has been released.


Note You need to log in before you can comment on or make changes to this bug.