Red Hat Bugzilla – Bug 1323679
rbac: Logging in as Administrator Role missing access to some tabs
Last modified: 2016-07-13 05:11:22 EDT
Description of problem: Administrator role has no access to containers Version-Release number of selected component (if applicable): 5.5.3.2 How reproducible: 100% Steps to Reproduce: 1. Create a used in the Administrator (not super-administrator) role 2. Login 3. Actual results: Containers top level nav is missing Expected results: Containers top level nav should be there Additional info:
As per the product feature tree, the administrator role does not have access to container, middleware, and RHI so when you login with the user having administrator role,these subtabs are not displayed.
"Actual results: Containers top level nav is missing" Containers are no longer top-level. They are under "Compute"
Ok, you probably did not mean "Top-level" I see the problem.
RHI, the plugin author can add the permission by adding those to db/fixtures/miq_product_roles/redhat_access_user_roles.yml
https://github.com/ManageIQ/manageiq/pull/8517
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/3b7a24756159d1330f0e1841ba5f1461b293a518 commit 3b7a24756159d1330f0e1841ba5f1461b293a518 Author: Martin Povolny <mpovolny@redhat.com> AuthorDate: Fri May 6 15:11:17 2016 +0200 Commit: Martin Povolny <mpovolny@redhat.com> CommitDate: Fri May 6 16:07:00 2016 +0200 Containers and Middleware features for admin. Admin user should have middleware and containers by default. https://bugzilla.redhat.com/show_bug.cgi?id=1323679 db/fixtures/miq_product_features.yml | 222 +++++++++++++++++------------------ db/fixtures/miq_user_roles.yml | 18 +++ 2 files changed, 129 insertions(+), 111 deletions(-)
https://github.com/ManageIQ/manageiq/pull/8541
https://github.com/ManageIQ/manageiq/pull/8473
Good to go. Verified and working fine in 5.6.0.9-rc2.20160531154046_b4e2f6d. Container navigation is displayed in the menu option for Administrator Role. There is some issues with RHI, which I am currently investigating, will log an BZ if it turns out to be a bug. Moving this issue to verified state based on the description of this bug.
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/RHBA-2016:1348