Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

Created attachment 1136493 [details]
no_buttons

Moving 6.2 bugs out to sat-backlog.

Upstream bug assigned to oprazak

Upstream bug assigned to oprazak

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?

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