Bug 1483240 - Unable to delete users logged in via ldap usergroups with org and/or loc set
Summary: Unable to delete users logged in via ldap usergroups with org and/or loc set
Keywords:
Status: CLOSED DUPLICATE of bug 1496294
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: LDAP
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-19 14:30 UTC by Kedar Bidarkar
Modified: 2019-08-12 16:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-27 19:20:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
unknown member type 500 ISE issue (21.12 KB, text/plain)
2017-08-19 14:35 UTC, Kedar Bidarkar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21030 0 None None None 2017-09-20 10:38:38 UTC

Description Kedar Bidarkar 2017-08-19 14:30:28 UTC
Description of problem:

Unable to delete users logged in via ldap usergroups with org and loc set


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

Sat6.3.0-snap11.0

How reproducible:


Steps to Reproduce:
1. Create a ldap-auth-source with org and loc
2. create a usergroup and add external user-group to it
3. login to sat6 via a user belonging to the user-group added in step 2.

Actual results:

Unable to delete users logged in via ldap usergroups with org and loc set

Oops, we're sorry but something went wrong "Unknown member type"

2017-08-19 10:11:25 9c97c263 [app] [I] Current user: admin (administrator)
2017-08-19 10:11:26 9c97c263 [app] [W] Action failed
 | ArgumentError: Unknown member type 
 | /usr/share/foreman/app/models/usergroup_member.rb:108:in `find_all_affected_memberships_for'
 | /usr/share/foreman/app/models/usergroup_member.rb:96:in `find_all_affected_memberships'
 | /usr/share/foreman/app/models/usergroup_member.rb:69:in `recache_memberships'
 | /usr/share/foreman/app/models/usergroup_member.rb:65:in `remove_old_cache'
 | /opt/rh/rh-ror42/root/usr/share/gems/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:432:in `block in make_lambda'
 | /opt/rh/rh-ror42/root/usr/share/gems/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:228:in `block in halting_and_conditional'
 | /opt/rh/rh-ror42/root/usr/share/gems/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:506:in `block in call'

2017-08-19 10:11:26 9c97c263 [app] [I] Deface: [WARNING] No :original defined for 'change 500 page content', you should change its definition to include:
 |  :original => '35d2b4f7aac0c083740c6de6775473457e9ae9d8' 
2017-08-19 10:11:26 9c97c263 [app] [I]   Rendered common/500.html.erb within layouts/application (11.5ms)
2017-08-19 10:11:26 9c97c263 [app] [I]   Rendered layouts/_application_content.html.erb (0.7ms)
2017-08-19 10:11:26 9c97c263 [app] [I]   Rendered layouts/base.html.erb (3.4ms)
2017-08-19 10:11:26 9c97c263 [app] [I] Completed 500 Internal Server Error in 156ms (Views: 26.7ms | ActiveRecord: 20.8ms)

This issue is only seen for users from ldap auth source , for both when only organization is set and also when location is set.

Expected results:

Should be able to delete users logged in via ldap usergroups with org and loc context set.


Additional info:

Comment 1 Kedar Bidarkar 2017-08-19 14:35:48 UTC
Created attachment 1315756 [details]
unknown member type 500 ISE issue

Comment 3 Brad Buckingham 2017-08-22 17:05:05 UTC
Is this a regression?

Comment 4 Kedar Bidarkar 2017-08-23 14:22:37 UTC
I am not sure, will need to check on a sat6.2 box and update it here.

Comment 6 Daniel Lobato Garcia 2017-09-20 10:38:36 UTC
Created redmine issue http://projects.theforeman.org/issues/21030 from this bug

Comment 7 Marek Hulan 2017-09-27 19:20:45 UTC
It is not a regression and in fact, it's a duplicate of BZ 1496294, closing as such. Prefering the later opened since it has CC attached.

*** This bug has been marked as a duplicate of bug 1496294 ***


Note You need to log in before you can comment on or make changes to this bug.