Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionChristian Marineau
2016-11-29 21:23:46 UTC
Created attachment 1226063[details]
Error from WebUI
Description of problem:
When assigning 6 roles or more to a user who is not admin, it will throw an error when he logs on:
Oops, we're sorry but something went wrong
Version-Release number of selected component (if applicable):
Satellite 6.2.X
Steps to Reproduce:
1. Create a user
2. Add 6 random roles, do not make him admin
3. Log on as the new user, an error will occur.
Actual results:
Oops, we're sorry but something went wrong PG::Error: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 1: ...ocation')) ORDER BY filters.role_id, filters.id, "roles"."n... ^ : SELECT DISTINCT "filters".* FROM "filters" INNER JOIN "filterings" ON "filterings"."filter_id" = "filters"."id" INNER JOIN "permissions" ON "permissions"."id" = "filterings"."permission_id" INNER JOIN "roles" ON "filters"."role_id" = "roles"."id" INNER JOIN "cached_user_roles" ON "roles"."id" = "cached_user_roles"."role_id" LEFT JOIN taxable_taxonomies ON (filters.id = taxable_taxonomies.taxable_id AND taxable_type = 'Filter') LEFT JOIN taxonomies ON (taxonomies.id = taxable_taxonomies.taxonomy_id) WHERE "roles"."builtin" = 0 AND "roles"."id" IN (7, 6, 8, 18, 17, 2) AND "cached_user_roles"."user_id" = $1 AND (permissions.resource_type = 'Role') AND (permissions.name = 'view_roles') AND (taxable_taxonomies.id IS NULL OR (taxonomies.type = 'Organization') OR (taxonomies.type = 'Location')) ORDER BY filters.role_id, filters.id, "roles"."name" ASC
Expected results:
No error when user log on
Additional info:
As a workaround, a specific role could be create to avoid adding so many roles.
Created attachment 1226063 [details] Error from WebUI Description of problem: When assigning 6 roles or more to a user who is not admin, it will throw an error when he logs on: Oops, we're sorry but something went wrong Version-Release number of selected component (if applicable): Satellite 6.2.X Steps to Reproduce: 1. Create a user 2. Add 6 random roles, do not make him admin 3. Log on as the new user, an error will occur. Actual results: Oops, we're sorry but something went wrong PG::Error: ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 1: ...ocation')) ORDER BY filters.role_id, filters.id, "roles"."n... ^ : SELECT DISTINCT "filters".* FROM "filters" INNER JOIN "filterings" ON "filterings"."filter_id" = "filters"."id" INNER JOIN "permissions" ON "permissions"."id" = "filterings"."permission_id" INNER JOIN "roles" ON "filters"."role_id" = "roles"."id" INNER JOIN "cached_user_roles" ON "roles"."id" = "cached_user_roles"."role_id" LEFT JOIN taxable_taxonomies ON (filters.id = taxable_taxonomies.taxable_id AND taxable_type = 'Filter') LEFT JOIN taxonomies ON (taxonomies.id = taxable_taxonomies.taxonomy_id) WHERE "roles"."builtin" = 0 AND "roles"."id" IN (7, 6, 8, 18, 17, 2) AND "cached_user_roles"."user_id" = $1 AND (permissions.resource_type = 'Role') AND (permissions.name = 'view_roles') AND (taxable_taxonomies.id IS NULL OR (taxonomies.type = 'Organization') OR (taxonomies.type = 'Location')) ORDER BY filters.role_id, filters.id, "roles"."name" ASC Expected results: No error when user log on Additional info: As a workaround, a specific role could be create to avoid adding so many roles.