Bug 1317806

Summary: Not allowed to promote/remove a content view version
Product: Red Hat Satellite Reporter: Kenny Tordeurs <ktordeur>
Component: Users & RolesAssignee: Ondřej Pražák <oprazak>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.7CC: ktordeur, szadok, thomas.betrancourt
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: UnusedFlags: ktordeur: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-25 07:49:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
role_filters
none
no_buttons none

Description Kenny Tordeurs 2016-03-15 09:36:02 UTC
Created attachment 1136492 [details]
role_filters

Description of problem:
a Role which allows Users to Promote or Remove a version was defined but on the version list page of a Content view, Users can't Promote or Remove a content view version as the buttons are not shown.

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

How reproducible:
100%

Steps to Reproduce:
1.Define a role that allows: publish,promote,deleting of content views
2. Try to delete/promote a content view version with a user that has that role assigned.


Actual results:
Unable to publish,promote,delete content views

Expected results:
Be able to publish,promote,delete content views

Additional info:
Screenshots attached

Comment 1 Kenny Tordeurs 2016-03-15 09:36:27 UTC
Created attachment 1136493 [details]
no_buttons

Comment 2 Bryan Kearney 2016-07-26 19:01:47 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 3 Satellite Program 2017-01-12 11:10:19 UTC
Upstream bug assigned to oprazak

Comment 4 Satellite Program 2017-01-12 11:10:23 UTC
Upstream bug assigned to oprazak

Comment 5 Ondřej Pražák 2017-01-18 11:37:17 UTC
It turns out the described behaviour is by design. You need to add a filter with resource type 'Lifecycle Environment' and permission promote_or_remove_content_views_to_environments, which restricts environments you are allowed to promote to.

Does this solve the issue for you?

Comment 6 Ondřej Pražák 2017-01-25 07:49:09 UTC
Closing, this is not a bug as per discussion in upstream [1]. I raised an issue to add this to our docs [2]

[1] https://github.com/Katello/katello/pull/6536#issuecomment-272987395
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1416294