Bug 1416154 - visibility options do not affect service buttons
Summary: visibility options do not affect service buttons
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: All
OS: All
Target Milestone: GA
: cfme-future
Assignee: Jozef Zigmund
QA Contact: Shveta
Whiteboard: service
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-24 17:27 UTC by Felix Dewaleyne
Modified: 2020-04-15 15:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-24 17:55:54 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)

Description Felix Dewaleyne 2017-01-24 17:27:11 UTC
Description of problem:
visibility options do not affect service buttons

Version-Release number of selected component (if applicable):

How reproducible:
all the time

Steps to Reproduce:
1.set up a service and provision it a couple times
2.set up another user with a different role 
3.assign one service to the other user
4. create a button outside of a button group for a service tha should only be visible to the admin role
5. log in as the second user and view his service

Actual results:
the button is displayed

Expected results:
the button is not displayed

Additional info:

Comment 2 Harpreet Kataria 2017-01-24 21:48:25 UTC

I was not able to recreate this issue on upstream master codebase, can you please try to recreate on We can discuss further if needed once you recreate the issue. 


Comment 3 Felix Dewaleyne 2017-02-07 09:57:28 UTC
reproduced against - that version is affected.

Comment 4 Jozef Zigmund 2017-02-13 17:43:50 UTC
Hi Felix, I think the problem could be settings of the Role. You need to set "VM & Template Access Restriction" (on 5.6.z), "Access Restriction for Services, VMs, and Templates" (on current master) to "Only User Owned" or "Only User or Group Owned" (depends what's expected restriction), than you could see expected result. Can you verify it ?

Note You need to log in before you can comment on or make changes to this bug.