Bug 860452

Summary: Deleting resources doesnot delete the permission tags
Product: Red Hat Satellite Reporter: Partha Aji <paji>
Component: Content ManagementAssignee: Dmitri Dolguikh <dmitri>
Status: CLOSED UPSTREAM QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: dmitri, mmccune
Target Milestone: UnspecifiedKeywords: 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: 2013-09-19 18:19:28 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:

Description Partha Aji 2012-09-25 20:45:56 UTC
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.)

Comment 2 Dmitri Dolguikh 2013-01-31 09:39:29 UTC
fixed in d318bcbf8eb3c14044688ac63c96dbadcbbeee82, 3f5530decd8bf97149685fdec81f4898f79b0eb0, c80d15a13382b75d7ebc3354a99c3aeb6483d062, 874512a9a0e1fdbc2802df415c62d5a5db499d41, 2bd0c58cdd92fd029f79c93b01ccee58b39fdcbd

Comment 3 Mike McCune 2013-08-16 18:02:14 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 4 Mike McCune 2013-09-19 18:19:28 UTC
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.