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:
Delete resource artificats like org/env/provider/system groups doesnot delete permission which have tags associated with those permissions

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Login as admin
2. create a custom provider X
3. create a role Y
4. Add a permission to  role Y to read/modify provider X
5. Delete provider X
6). Expand Role y

Actual results:
Notice that the permission associated to provider X still exists

Expected results:
The permission associated to provider X must get wiped out since provder X was deleted.

Additional info:
Similar case for Org/Environment/System Groups (the tags end up staying in the permissions even though the resource themselves were deleted.)

fixed in d318bcbf8eb3c14044688ac63c96dbadcbbeee82, 3f5530decd8bf97149685fdec81f4898f79b0eb0, c80d15a13382b75d7ebc3354a99c3aeb6483d062, 874512a9a0e1fdbc2802df415c62d5a5db499d41, 2bd0c58cdd92fd029f79c93b01ccee58b39fdcbd

getting rid of 6.0.0 version since that doesn't exist

These bugs have been resolved in upstream projects for a period of months so
I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to
re-open.