Bug 971140
| Summary: | Permission to delete content view not allowing user to actually remove them | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jeff Weiss <jweiss> |
| Component: | WebUI | Assignee: | Partha Aji <paji> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | Nightly | CC: | cwelton, dajohnso, jmontleo, mmccune, tkolhar |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-02 14:06:39 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: | |
| Embargoed: | |||
As of today Content View Definitions (CVD) and Content Views (CV) have different delete criteria CVD can be deleted if you have Administer/Delete permissions CV can be deleted if you have Publish permission on CVD that published the CV. Checking with Mike if the status quo is what we want. I am ok with saying, lets make it more uniform by saying CV can be deleted if you have Publish/Delete permission on CVD that published the CV. In my opinion we should unify the permissions such that if you can CRUD the CVDs you should also be able to CRUD the views published from them. Cool. Changing the code to all CV to be deleted if you have CVD delete or publish. should be fixed when https://github.com/Katello/katello/pull/3009 gets merged to master Moving this to be tested during MDP3, not critical for MDP2 success story VERIFIED This was delivered with 6.0.3, which is the Satellite 6 Beta. |
Description of problem: Version-Release number of selected component (if applicable): 1.4.2-1.git.552.b351354.el6 How reproducible: Steps to Reproduce: 1. Create a role and user and a content view. 2. Assign the user to the role, and give the role the following global permissions: [{:resource-type "Content View Defintions", :verbs ["Read Content View Definitions" "Delete Content View Definitions"]}] 3. Log in as the user. Try to delete the content view Actual results: There is no Remove link after the content view is selected. Expected results: User is able to remove the content view. Additional info: