Bug 967799
Summary: | Beaker shows a 500 error when modifying group name to a name which already exists | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | xjia <xjia> |
Component: | web UI | Assignee: | Amit Saha <asaha> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nick Coghlan <ncoghlan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | develop | CC: | asaha, dcallagh, ebaak, llim, qwan, rglasz, rmancy, szhou, xtian |
Target Milestone: | 0.13 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | UX | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-25 06:27:08 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
xjia
2013-05-28 11:10:27 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. On Gerrit: http://gerrit.beaker-project.org/#/c/2007/2 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 Beaker 0.13.1 has been released. |