Bug 2218290 - promote_or_remove_content_views and promote_or_remove_content_views_to_environments both role needs to be renamed or merged
Summary: promote_or_remove_content_views and promote_or_remove_content_views_to_enviro...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.11.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-28 15:17 UTC by yopatil@redhat.com
Modified: 2023-06-30 00:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-18706 0 None None None 2023-06-29 13:12:46 UTC

Description yopatil@redhat.com 2023-06-28 15:17:10 UTC
Description of problem:
[RFE] promote_or_remove_content_views and promote_or_remove_content_views_to_environments both role needs to be renamed or merged


How reproducible:

1. Create a role "lifecycle Role" with permissions  "publish_content_views" and "promote_or_remove_content_views"

2. set it to the user "ansible_provsion", but this user is unable to use the promote option. 

3. Along with this role, below standard roles are also set for the user.
Roles:
    Edit hosts
    Viewer
    View hosts


Actual results:

Scenario1.:
With this permission set user is able to promote and publish a new version as below:
Go to content >> content view >> select the cv >> publish new version >> enable the promote tab

Scenario2:
If we click on the existing version of any CV and try to publish it he is getting the below error:

Error: Could not find content_view_version resource with id 4. Potential missing permissions: promote_or_remove_content_views, promote_or_remove_content_views_to_environments

4. Now, if we add promote_or_remove_content_views_to_environments permission then the user can perform both scenarios.


Expected results:
Either these roles should be merged or renamed so that it will serve their purpose as expected.
that is,
- promote_or_remove_content_views: Only for new versions. 
- promote_or_remove_content_views_to_environments: for all including existing.


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