Project

General

Profile

Actions

Bug #9878

closed

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

Added by Marek Hulán about 9 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
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 1 (0 open1 closed)

Related to Foreman - Bug #10123: Api::V2::ExternalUsergroupsControllerTest fails with "Render and/or redirect were called multiple times"ClosedDaniel Lobato Garcia04/13/2015Actions
Actions #1

Updated by Marek Hulán about 9 years ago

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

Updated by The Foreman Bot about 9 years ago

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

Updated by Marek Hulán about 9 years ago

  • Priority changed from High to Normal
  • translation missing: en.field_release 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

Actions #4

Updated by Dominic Cleal about 9 years ago

  • translation missing: en.field_release deleted (28)

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

Actions #5

Updated by Marek Hulán about 9 years ago

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

Updated by Dominic Cleal about 9 years ago

  • translation missing: en.field_release set to 28
Actions #7

Updated by Dominic Cleal about 9 years ago

  • translation missing: en.field_release changed from 28 to 50
Actions #8

Updated by Dominic Cleal about 9 years ago

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

Also available in: Atom PDF