Bug 766647 - duplicate env creation - better error message needed
Summary: duplicate env creation - better error message needed
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Katello
Classification: Retired
Component: Webservice API
Version: 1.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 1.0
Assignee: Petr Chalupa
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-12 14:23 UTC by Garik Khachikyan
Modified: 2015-05-05 01:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-17 13:09:54 UTC


Attachments (Terms of Use)

Description Garik Khachikyan 2011-12-12 14:23:37 UTC
Description of problem:
execute `environment create --name Dev1 --org ACME_Corporation --prior=Locker` two times
On the second execution error is returning back:
---
Validation failed: Environments is invalid
---


Version-Release number of selected component (if applicable):
katello-0.1.135-2.el6.x86_64
katello-cli-0.1.23-3.el6.noarch
candlepin-0.5.4-1.el6.noarch
pulp-0.0.254-4.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. see above
2.
3.
  
Actual results:
error like "Validation failed: Environments is invalid"

Expected results:
a message telling user about environment name already taken or so.

Additional info:

Comment 1 Petr Chalupa 2012-04-24 08:21:39 UTC
fixed in 52e93499e123243cf3d800b21472790bea9e622d

Comment 2 Sachin Ghai 2012-05-16 07:24:43 UTC
verified with following katello build:

katello-0.2.35-1.el6.noarch

Error message is improved now, following message appeared when we can create duplicate env:

katello> environment create --name test --prior Library --org ACME_Corporation
Successfully created environment [ test ]
katello> environment create --name test --prior Library --org ACME_Corporation
Validation failed: Name must be unique within one organization

Comment 3 Bryan Kearney 2012-07-17 13:09:54 UTC
Moving all community bugs with fixes to closed.


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