Bug 1097683

Summary: LDAP: Trying to create an LDAP instance with the name 'Internal' returns confusing message.
Product: Red Hat Satellite Reporter: Corey Welton <cwelton>
Component: Users & RolesAssignee: Dominic Cleal <dcleal>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.3CC: bbuckingham, bkearney
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/6536
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-04 17:49:43 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 Corey Welton 2014-05-14 10:22:08 UTC 
Description of problem:
When trying to create/associate an LDAP source that has the name "Internal", user is told that the name "has already been taken" -- this despite perhaps never having set up an LDAP source before at all.

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140508.1

How reproducible:


Steps to Reproduce:
1.  Attempt to create a new LDAP source.  Give this source the name "Internal"
2.  Fill in other details; submit
3.  View results.

Actual results:

name cannot be used because "has already been taken"

Expected results:

I assume that the term "Internal" might probably be reserved or something, not sure.  In any case, we should tell users they can't use that term, or provide some context indicating why exactly "Internal" can't be used.

Additional info:
Comment 2 Dominic Cleal 2014-07-09 10:01:12 UTC 
Created redmine issue http://projects.theforeman.org/issues/6536 from this bug
Comment 3 Bryan Kearney 2015-08-25 17:56:41 UTC 
Upstream bug component is Provisioning
Comment 4 Bryan Kearney 2015-08-25 17:58:16 UTC 
Upstream bug component is Users & Roles
Comment 5 Bryan Kearney 2017-01-04 17:49:43 UTC 
This is an older bug, which is being tracked upstream. We will not be tracking this downstream. When the upstream issue is resolved, the next rebase will pull in the fix.