Description of problem:
Attempted to search for specific package in product content in Sat 6 Content search and PGError ambiguous reference to id is displayed. See attached screenshot and foreman production.log snippet.
Version-Release number of selected component (if applicable):
Sat 6.0.3 Beta
RHEL 6.5 2.6.32-431.20.3
Steps to Reproduce:
1. Assuming pre-built Sat 6.0.3 with manifest uploaded, content syned, custom content synced, content views published/promoted
2. Navigate to content search, select Products under content, and attempt to search for a package under products.
PG Error is displayed on browser and error is dumped to foreman/production.log
Content is searched and no error is displayed.
I have published/promoted a minimum of 99 content views.
Created attachment 918728 [details]
foreman production.log with debug logging
Created attachment 918729 [details]
Screenshot of error in UI.
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
(In reply to Alex Krzos from comment #0)
> Additional info:
> I have published/promoted a minimum of 99 content views.
In case it helps: I just hit this having published/promoted no content views yet, just sync'd a RHEL repo into the Library, went to search for a package, selected the auto-complete for repos and the error appeared as soon as I started typing:
PGError: ERROR: column reference "id" is ambiguous LINE 1: SELECT id FROM "katello_repositories" INNER JOIN "katello_pr... ^ : SELECT id FROM "katello_repositories" INNER JOIN "katello_products" ON "katello_products"."id" = "katello_repositories"."product_id" INNER JOIN "katello_content_view_versions" ON "katello_content_view_versions"."id" = "katello_repositories"."content_view_version_id" WHERE "katello_content_view_versions"."content_view_id" IN (1, 2) AND "katello_repositories"."product_id" IN (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18) ORDER BY katello_repositories.name ASC (ActiveRecord::StatementInvalid)
*** This bug has been marked as a duplicate of bug 1115308 ***