This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
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: CLOSED MIGRATED
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: 2024-06-06 16:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:23:25 UTC
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 Migrated None 2024-06-06 16:23:23 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.

Comment 2 Eric Helms 2024-06-06 16:23:25 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


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