Bug 2218290
| Summary: | promote_or_remove_content_views and promote_or_remove_content_views_to_environments both role needs to be renamed or merged | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | yopatil <yopatil> |
| Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | NEW --- | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.11.5 | CC: | mhulan, oezr, rlavi, sajha |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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.