Bug 1517954 - Unable to use the same tenant name across multiple regions.
Summary: Unable to use the same tenant name across multiple regions.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.7.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: GA
: 5.9.0
Assignee: Gregg Tanzillo
QA Contact: Pavol Kotvan
URL:
Whiteboard: distributed:cfme_tenant
Depends On: 1422901
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-27 18:10 UTC by Satoe Imaishi
Modified: 2021-06-10 13:42 UTC (History)
9 users (show)

Fixed In Version: 5.9.0.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1422901
Environment:
Last Closed: 2018-03-01 13:21:45 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2939501 0 None None None 2017-11-27 18:11:20 UTC
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Comment 2 CFME Bot 2017-11-29 20:24:35 UTC 
New commit detected on ManageIQ/manageiq/gaprindashvili:
https://github.com/ManageIQ/manageiq/commit/c7f04c7c9dce3afd015c212057a6025bd2828973

commit c7f04c7c9dce3afd015c212057a6025bd2828973
Author:     Jason Frey <fryguy9>
AuthorDate: Mon Nov 27 11:08:06 2017 -0500
Commit:     Satoe Imaishi <simaishi>
CommitDate: Mon Nov 27 13:12:40 2017 -0500

    Merge pull request #16506 from gtanzillo/tenant-name-unique-in-region
    
    Scope Tenant#name validation to the current region
    (cherry picked from commit b3beb05a366986f8e6626f7971994cca49824a6c)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1517954

 app/models/tenant.rb       | 4 +++-
 spec/models/tenant_spec.rb | 9 +++++++++
 2 files changed, 12 insertions(+), 1 deletion(-)
Comment 5 errata-xmlrpc 2018-03-01 13:21:45 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://access.redhat.com/errata/RHSA-2018:0380
Note You need to log in before you can comment on or make changes to this bug.