Bug 1399208

Summary: [Multi-tenancy] - RFE - Disable renaming of Tenants created by tenant mapping
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvidersAssignee: Libor Pichler <lpichler>
Status: CLOSED ERRATA QA Contact: Pavol Kotvan <pakotvan>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7.0CC: cpelland, hkataria, jfrey, jhardy, lpichler, mpovolny, obarenbo, simaishi
Target Milestone: GAKeywords: FutureFeature, ZStream
Target Release: 5.7.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:tenant_cfme
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1382687 Environment:
Last Closed: 2017-02-27 19:25:02 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:
Bug Depends On: 1382687    
Bug Blocks:    

Comment 2 CFME Bot 2017-01-06 14:30:52 UTC
New commit detected on ManageIQ/manageiq/euwe:

commit b377888762bb89af67e5382f035710eecc6a4c89
Author:     Milan Z√°zrivec <mzazrivec>
AuthorDate: Fri Oct 14 11:38:28 2016 +0200
Commit:     Satoe Imaishi <simaishi>
CommitDate: Fri Jan 6 09:29:51 2017 -0500

    Merge pull request #11931 from lpichler/disable_tenant_edit_from_cloud_tenant_mapping
    Disable tenant edit from cloud tenant mapping
    (cherry picked from commit e91a3022b4606a5954261627532534c8a90a02cf)

 .../application_helper/button/tenant_edit.rb       |  7 +++++++
 .../application_helper/toolbar/tenant_center.rb    |  3 ++-
 spec/factories/tenant.rb                           |  4 ++++
 .../application_helper/buttons/tenant_edit_spec.rb | 22 ++++++++++++++++++++++
 4 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 app/helpers/application_helper/button/tenant_edit.rb
 create mode 100644 spec/helpers/application_helper/buttons/tenant_edit_spec.rb

Comment 6 errata-xmlrpc 2017-02-27 19:25:02 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.