Description of problem: When a Beaker user account is (marked as) removed, its group memberships are still left behind. Version-Release number of selected component (if applicable): 20.2 How reproducible: easily Steps to Reproduce: 1. Create a user account and add them to a group. 2. Remove the account (Admin -> Accounts in the web UI then click Remove, or use bkr remove-account). 3. Check the membership list for the group. Actual results: The removed user is still present. Expected results: The removed user should be removed from all groups as well, with a suitable activity record indicating that they were removed from each group. Additional info: This bug is really cosmetic only, since a removed user still cannot log in and their outstanding reservations and loans and systems are changed when they are removed. The patch needs to include a db migration which will find existing removed accounts and clean up their group memberships, with a suitable activity entry.
Need to remove the user from all access policies as well.
Going to target this for develop only, because there are a lot of changes to the group code from release-21 -> develop.
Well the db migration was a lot harder than I expected... Patch posted for review: http://gerrit.beaker-project.org/4516 although I will need to fix it up a bit after inverted groups (bug 1220610) lands.
This bug fix is included in beaker-server-22.0-0.git.113.08aeea9 which is currently available for testing here: https://beaker-devel.app.eng.bos.redhat.com/
Beaker 22.0 has been released.