Bug 807055

Summary:	Environment names should be freely renamable
Product:	Red Hat Satellite	Reporter:	Todd Warner <taw>
Component:	WebUI	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	mmccune
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-18 15:29:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Todd Warner 2012-03-26 21:29:08 UTC

In 1.0 (well, Beta6) I try to change the environment name. I get a validation error with no explanation (that's a bug unto itself), but then I find these bugs: bug 787226 and bug 795928.

Apparently one can't change the name of an environment because it is linked to its repoID. If this is the case, this is a design flaw. Names (or labels) need to be editable for nearly all objects that one can edit details about within the system. Separately, there needs to be a unique and immutable ID. One is for humans, the other is for uniqueness and machines.

Now, it would be sensible to warn an admin of a potential conflict (like if I wanted to call three environments "Dev". Warn, but not disallow.

Comment 1 Justin Sherrill 2012-12-18 15:29:31 UTC


*** This bug has been marked as a duplicate of bug 795928 ***