Bug 1395667

Summary: User search using usergroup do not work
Product: Red Hat Satellite Reporter: Roman Bobek <rbobek>
Component: SearchAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.4CC: andrew.schofield, bbuckingham, cmarinea, dhlavacd, gapatil, jcallaha, lzap, mhulan, oshtaier
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:59:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error message from production.log none

Description Roman Bobek 2016-11-16 11:51:33 UTC
Created attachment 1221112 [details]
error message from production.log

Description of problem:
When searching users using usergroup, Satellite returns following error:

2016-11-16 13:57:58 [app] [W] Action failed
 | ActiveRecord::StatementInvalid: PG::Error: ERROR:  column "member_type" does not exist
 | LINE 3: ...."id" = "cached_usergroup_members"."user_id"  AND member_typ...
 |                                                              ^
 | : SELECT  DISTINCT "users"."id", firstname AS alias_0 FROM "users" LEFT OUTER JOIN "cached_usergroup_members" ON "cached_usergroup_members"."user_id" = "users"."id" LEFT OUTER JOIN "usergroups" ON "usergroups"."id" = "cached_usergroup_members"."usergroup_id" LEFT OUTER JOIN "auth_sources" ON "auth_sources"."id" = "users"."auth_source_id" WHERE "users"."id" IN (4, 1, 2, 3) AND ("users"."auth_source_id" NOT IN (2)) AND (("users"."id" IN (SELECT "users"."id" FROM         "users"
 |         INNER JOIN "cached_usergroup_members"
 |         ON "users"."id" = "cached_usergroup_members"."user_id"  AND member_type = 'User'
 |         INNER JOIN "usergroups"
 |         ON "cached_usergroup_members"."usergroup_id" = "usergroups"."id"
 |  WHERE "usergroups"."name" = 'penguins' )))  ORDER BY firstname LIMIT 20 OFFSET 0
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `exec'

(full error message with ruby backtrace is enclosed to the BZ)


Version-Release number of selected component (if applicable):
Reproduced on:
* Red Hat Satellite 6.2.3
* Red Hat Satellite 6.2.4


How reproducible:
Always


Steps to Reproduce:
1. Create a usergroup (Administer > User groups > New User Group)
2. Add a user to the user group
3. Sear for users belonging to the user group (Administer > Users > enter 'usergroup = <usergroupname>' in the search field and hit search)


Actual results:
The search will fail and Satellite reports above mentioned error.


Expected results:
All users belonging to the usergroup should be listed.

Comment 1 Marek Hulan 2016-11-16 14:55:52 UTC
Created redmine issue http://projects.theforeman.org/issues/17364 from this bug

Comment 2 Bryan Kearney 2016-11-16 15:05:15 UTC
Upstream bug assigned to mhulan

Comment 3 Bryan Kearney 2016-11-16 15:05:18 UTC
Upstream bug component is Search

Comment 4 Bryan Kearney 2016-11-16 15:05:21 UTC
Upstream bug assigned to mhulan

Comment 6 Christian Marineau 2016-12-12 13:50:04 UTC
*** Bug 1400713 has been marked as a duplicate of this bug. ***

Comment 7 Bryan Kearney 2016-12-18 17:04:44 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17364 has been resolved.

Comment 10 Oleksandr Shtaier 2017-06-30 11:12:38 UTC
Verified for latest 6.3 by test automation script.

Steps:
1. Create two new users
2. Create new user group with assigned user created in previous step
3. Search for users (Administer > Users) by usergroup (usergroup = `user_group_name`)
4. Also check that no error is raised on the page

Comment 11 Bryan Kearney 2018-02-21 16:59: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-2018:0336