Bug 1132730

Summary:	no activity records showing access policy rules being removed when a group is removed
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	web UI	Assignee:	Amit Saha <asaha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.17	CC:	aigao, asaha, dcallagh, ebaak, rmancy, xma
Target Milestone:	0.18	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-04 05:40:33 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 Dan Callaghan 2014-08-21 23:47:15 UTC

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

How reproducible:
easily

Steps to Reproduce:
1. Find (or create) a Beaker group which has been used in the rules for a system's access policy
2. Delete the group (Admin -> Groups, then Remove) or perhaps accidentally delete the group due to bug 1132729
3. Check system access policy and activity records

Actual results:
Group no longer appears in the access policy (as expected) but the activity log does not show the rules being removed. As a result there is no way to see what they were prior to removal.

Expected results:
Group should be removed from the access policy, and any access policy rules which were removed should be recorded in system activity like normal rule removal.

Comment 3 Amit Saha 2014-08-26 01:09:43 UTC

http://gerrit.beaker-project.org/#/c/3275/

Comment 6 Dan Callaghan 2014-09-04 05:40:33 UTC

This bug fix was applied to the release-0.17 branch, but we are not doing any more maintenance releases of the 0.17.x series. So this bug is fixed in Beaker 0.18.0.