Project

General

Profile

Bug #9878

Deleteing an external AD user-group should disassociate the users from the user-group associated

Added by Marek Hulán over 6 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1195607
Description of problem:
Deleteing an external AD user-group should disassociate the users from the user-group which was associated to.

Version-Release number of selected component (if applicable):
sat6.1 Beta snap3

How reproducible:
deleting an external AD User-group from the CLI and checking the User-Group, it appears the users are still associated under the User-group.

Steps to Reproduce:
1. create an User-Group
2. Add an External AD User Group
3. Try logging in with some users of the above External AD UserGroup
4. Make sure the Users from AD are associated with the User-Group.
5. Now delete the External AD User Group
6. Note that the Users are still associated

Actual results:

Users are still associated, even after the deletion of the External AD User-group.

Expected results:

Users should get dis-associated, after the deletion of the External AD User-group.

Additional info:

Not sure 100% about the bug but feel let's track this issue here.


Related issues

Related to Foreman - Bug #10123: Api::V2::ExternalUsergroupsControllerTest fails with "Render and/or redirect were called multiple times"Closed2015-04-13

Associated revisions

Revision 22d2b02f (diff)
Added by Marek Hulán over 6 years ago

Fixes #9878 - refresh external usergroup on API manipulation

Revision a6312c86 (diff)
Added by Marek Hulán over 6 years ago

Fixes #9878 - refresh external usergroup on API manipulation

(cherry picked from commit 22d2b02fefc54228631008181c3d0db0b2360d28)

History

#1 Updated by Marek Hulán over 6 years ago

  • Category set to Users, Roles and Permissions
  • Status changed from New to Assigned

#2 Updated by The Foreman Bot over 6 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2261 added
  • Pull request deleted ()

#3 Updated by Marek Hulán over 6 years ago

  • Priority changed from High to Normal
  • Legacy Backlogs Release (now unused) set to 28

it's probably no high priority as the rake task would sync it later, but likely something that should be fixed in 1.8

#4 Updated by Dominic Cleal over 6 years ago

  • Legacy Backlogs Release (now unused) deleted (28)

Removing release flag as this isn't a regression, will set it after it's been closed.

#5 Updated by Marek Hulán over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#6 Updated by Dominic Cleal over 6 years ago

  • Legacy Backlogs Release (now unused) set to 28

#7 Updated by Dominic Cleal over 6 years ago

  • Legacy Backlogs Release (now unused) changed from 28 to 50

#8 Updated by Dominic Cleal over 6 years ago

  • Related to Bug #10123: Api::V2::ExternalUsergroupsControllerTest fails with "Render and/or redirect were called multiple times" added

Also available in: Atom PDF