Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
[User] - Ldap User not able to get deleted if it is assigned to multiple user groups and generated the 500 Internal Server Error 

Version-Release number of selected component (if applicable):
Satellite 6.7, 6.6 

How reproducible:
Always 

Steps to Reproduce:
1.Join the Ldap Authentication (Free IPA)
2.Create Multiple User Groups (test_group_1, test_group_2)
3. Create an IDM user and Logged into Satellite with that user.
4. Now assign that user to multiple groups.
5. try to delete that User from Satellite  

Actual results:
User is not able to get deleted and getting a 500 internal server error 

Expected results:
User should be able to get deleted 

Additional info:
It exists in Satellite 6.6

Created redmine issue https://projects.theforeman.org/issues/28858 from this bug

Upstream bug assigned to oezr

Upstream bug assigned to oezr

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28858 has been resolved.

Tested on Satellite 6.7 Snap 15 (foreman-1.24.1.14-1.el7sat.noarch) using the reproducer from the initial report. User got removed successfully, no error in WebUI nor in logs.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1454