Bug 1484901

Summary: [RFE] Include EvmRole-reader as read-only role in the fixtures
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ControlAssignee: Greg McCullough <gmccullo>
Status: CLOSED ERRATA QA Contact: Satyajit Bulage <sbulage>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.8.0CC: jhardy, obarenbo, sbulage, simaishi
Target Milestone: GAKeywords: FutureFeature, ZStream
Target Release: 5.8.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 5.8.2.0 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1480190 Environment:
Last Closed: 2017-10-24 00:40:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1480190    
Bug Blocks: 1480288    

Comment 2 CFME Bot 2017-08-24 13:51:15 UTC 
New commit detected on ManageIQ/manageiq/fine:
https://github.com/ManageIQ/manageiq/commit/531a8095e13819fadbc6c8682481ff28efd2e36b

commit 531a8095e13819fadbc6c8682481ff28efd2e36b
Author:     Dan Clarizio <dclarizi>
AuthorDate: Thu Jul 27 08:42:40 2017 -0700
Commit:     Satoe Imaishi <simaishi>
CommitDate: Thu Aug 24 09:48:39 2017 -0400

    Merge pull request #15647 from rsevilla87/master
    
    Include EvmRole-reader as read-only role in the fixtures
    (cherry picked from commit 78fb6b49aa6699b9d4e90ab14f2175a051c0c4fe)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1484901

 db/fixtures/miq_user_roles.yml    | 107 ++++++++++++++++++++++++++++++++++++++
 db/fixtures/role_map.yaml         |   1 +
 spec/models/miq_user_role_spec.rb |   2 +-
 3 files changed, 109 insertions(+), 1 deletion(-)
Comment 3 Satyajit Bulage 2017-09-05 13:03:29 UTC 
EvmRole-reader as read-only role is present in the fixtures with view access.

Verified Version: 5.8.2.0.20170824192913_b09a5f8
Comment 5 errata-xmlrpc 2017-10-24 00:40:39 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-2017:3005