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.
Bug 1753907 - The Foreman "forgets" group members after update to 1.22.0
Summary: The Foreman "forgets" group members after update to 1.22.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: LDAP
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.6.0
Assignee: Daniel Lobato Garcia
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 08:26 UTC by Ondřej Ezr
Modified: 2019-11-18 10:24 UTC (History)
4 users (show)

Fixed In Version: foreman-1.22.0.32-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:48:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
After upgrade - screenshot (21.97 KB, image/png)
2019-09-26 11:39 UTC, Nikhil Kathole
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27402 0 'High' 'Closed' 'The Foreman "forgets" group members after update to 1.22.0' 2019-12-06 09:41:19 UTC

Description Ondřej Ezr 2019-09-20 08:26:32 UTC
I've just updated from 1.21.3 to 1.22.0 and found that users got permission denied messages after logging in, for example because of missing "view_hosts" permissions. After logging in as admin I recognized that the groups didn't have any members anymore. So I added the members again, saved the change, reloaded the group again to verify (members where still there), logged out from admin and logged in as normal user -> No view_hosts permission. Logged back in as admin and saw that the group had no members again.

How reproducible:
always

Steps to Reproduce:
1. Set up LDAP authentication with synchronization enabled
2. Create simple Satellite Usergroup with no external user group link
3. Add users from the LDAP auth source to the Usergroup
4. Log-in as any of the LDAP users aded to the Usergroup

Actual results:
LDAP users are no longer members of the Satellite Usergroup.

Expected results:
No change in the Usergroup memberships.

Comment 1 Ondřej Ezr 2019-09-20 08:26:35 UTC
Created from redmine issue https://projects.theforeman.org/issues/27402

Comment 2 Ondřej Ezr 2019-09-20 08:26:39 UTC
Upstream bug assigned to oezr

Comment 6 Nikhil Kathole 2019-09-26 11:39:25 UTC
VERIFIED

version tested:
Satellite 6.6.0 snap 22

Was able to reproduce the issue with following steps:

On satellite 6.5,

1. Create ldap auth
2. Login with ldap User in satellite and logout
3. create usergroup and assign ldap user to it
4. perform upgrade
5. After upgrade ldap user was not part of user group

Tested with upgrade from 6.5 to 6.6 snap 22, ldap user user group membership not lost after upgrade.

Comment 7 Nikhil Kathole 2019-09-26 11:39:51 UTC
Created attachment 1619479 [details]
After upgrade - screenshot

Comment 8 Bryan Kearney 2019-10-22 19:48:01 UTC
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-2019:3172


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