Bug 1402902

Summary: Namespace: Name uniqueness validation is not case-insensitive, like other Automate objects.
Product: Red Hat CloudForms Management Engine Reporter: Milan Falešník <mfalesni>
Component: AutomateAssignee: Patrik Kománek <pkomanek>
Status: CLOSED CURRENTRELEASE QA Contact: Dmitry Misharov <dmisharo>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7.0CC: jhardy, mkanoor, obarenbo, simaishi, tfitzger
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: automate
Fixed In Version: 5.8.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1412291 (view as bug list) Environment:
Last Closed: 2017-06-12 16:41:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1412291    

Description Milan Falešník 2016-12-08 15:01:07 UTC 
Description of problem:
You can add a namespace next to other namespace, where ns_a.lower() == ns_b.lower(). Revealed during negative testing.

Other objects' matching in Automate is done case-insensitive including the paths to reference the Automate objects. This can potentially lead to a confusion.

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

How reproducible:
always

Steps to Reproduce:
0. Create a domain
1. Create a namespace in the domain, called Foo
2. Create a namespace in the domain, called foo

Actual results:
You can create such namespace

Expected results:
You should not be able to create such namespace.

Additional info:
Comment 2 Patrik Kománek 2017-01-05 15:07:06 UTC 
solved in https://github.com/ManageIQ/manageiq/pull/13146
Comment 4 Milan Falešník 2017-02-28 14:44:34 UTC 
Verified in 5.8.0.2. Now you cannot create such namespaces.