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.

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:

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.