Bug 740379 - Changesets should not be stored in history with 'Name' as the unique identifier.
Summary: Changesets should not be stored in history with 'Name' as the unique identifier.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Katello
Classification: Retired
Component: WebUI
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jason E. Rist
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-21 19:52 UTC by Corey Welton
Modified: 2011-09-28 19:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-28 19:47:51 UTC


Attachments (Terms of Use)

Description Corey Welton 2011-09-21 19:52:01 UTC
Description of problem:
If a user creates a changeset and goes through the motions, that changeset is saved in changeset history. However, from that point on, the name of this changeset is unique and can never be used again.  

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


How reproducible:


Steps to Reproduce:
1.  Create a new changeset called 'PushToDev' and add packages to it
2.  Promote this changeset
3.  Navigate to Changeset History; note the existence of your "PushToDev" changeset in the audit.
4.  Attempt to create a new changeset, also called 'PushToDev'
5.  Attempt to promote this changeset

Actual results:
Validation Failed:
Name Must be unique within an environment

Expected results:
Completed/archived Changesets should be stored with something else as the unique key, as to allow users to re-use names over and over again.  While namespace is basically infinite, it's evident that users can very quickly run out of 'convenient' namespace.

I'm also not sure why users are able to change Names (and possibly descriptions) in an apparently-archived Changset History audit trail, but that might be a different bug.

Additional info:

Comment 1 Mike McCune 2011-09-28 19:47:51 UTC
working as designed


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