Bug 1412291

Summary:	Namespace: Name uniqueness validation is not case-insensitive, like other Automate objects.
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	Automate	Assignee:	Patrik Kománek <pkomanek>
Status:	CLOSED ERRATA	QA Contact:	Shveta <sshveta>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.7.0	CC:	cpelland, jhardy, mkanoor, obarenbo, simaishi, sshveta, tfitzger
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	automate
Fixed In Version:	5.7.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1402902	Environment:
Last Closed:	2017-02-27 19:21:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:
Embargoed:
Bug Depends On:	1402902
Bug Blocks:

Comment 2 CFME Bot 2017-01-11 23:36:03 UTC

New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/1dcd2202647ee9f1c411d9f1ea34c9cd1ce1c0e8

commit 1dcd2202647ee9f1c411d9f1ea34c9cd1ce1c0e8
Author:     Madhu Kanoor <mkanoor>
AuthorDate: Thu Dec 22 11:33:45 2016 -0500
Commit:     Satoe Imaishi <simaishi>
CommitDate: Wed Jan 11 18:30:56 2017 -0500

    Merge pull request #13146 from pkomanek/modify_name_validation_for_a_new_automate_namespaces
    
    Making the Automate namespace name validation not to be case-sensitive.
    (cherry picked from commit ea9b4a30f2979051ad68581b151a3e80565cee16)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1412291

 .../models/miq_ae_namespace.rb                     |  2 +-
 .../models/miq_ae_namespace_spec.rb                | 28 ++++++++++++++++++++++
 2 files changed, 29 insertions(+), 1 deletion(-)

Comment 3 Shveta 2017-02-07 19:35:44 UTC

Duplicate namespace cannot be created.
Verified in 5.7.1.1.20170206165110_3c42361

Comment 5 errata-xmlrpc 2017-02-27 19:21:32 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2017-0320.html