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.
Description of problem:
There is a nasty traceback while searching for an existing hostname in Content Hosts using scoped search.
search query: "my-host-1.domain.org"
production.log:
2016-05-11 04:30:59 [app] [I] Processing by Api::V2::HostsController#index as JSON
2016-05-11 04:30:59 [app] [I] Parameters: {"organization_id"=>"1", "page"=>"1", "search"=>"my-host-1.lab.eng.brq.redhat.com", "sort_by"=>"name", "sort_order"=>"ASC", "apiv"=>"v2"}
2016-05-11 04:30:59 [app] [W] Action failed
| PG::Error: ERROR: missing FROM-clause entry for table "organizations_hosts"
| LINE 1: ...14_r9, "taxonomies"."katello_default" AS t14_r10, "organizat...
searching for non-existing hostname works fine.
Version-Release number of selected component (if applicable):
6.2.0 Beta GA10.1
How reproducible:
always
Steps to Reproduce:
1. register a host to your satellite so it appears in Content Hosts
2. Try to put its hostname to the search field and hit search
3. check production.log
Actual results:
ISE
Expected results:
Search query is being validated performed on all applicable fields.
Additional info:
Workaround is to use the explicit-field search query:
name = my-host-1.domain.org or
name ~ my-host-1.domain.org
- I'm requesting a blocker flag for this BZ as this will be hit quite often by users (single word search queries are the most commonly used)
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/RHBA-2016:1501
Description of problem: There is a nasty traceback while searching for an existing hostname in Content Hosts using scoped search. search query: "my-host-1.domain.org" production.log: 2016-05-11 04:30:59 [app] [I] Processing by Api::V2::HostsController#index as JSON 2016-05-11 04:30:59 [app] [I] Parameters: {"organization_id"=>"1", "page"=>"1", "search"=>"my-host-1.lab.eng.brq.redhat.com", "sort_by"=>"name", "sort_order"=>"ASC", "apiv"=>"v2"} 2016-05-11 04:30:59 [app] [W] Action failed | PG::Error: ERROR: missing FROM-clause entry for table "organizations_hosts" | LINE 1: ...14_r9, "taxonomies"."katello_default" AS t14_r10, "organizat... searching for non-existing hostname works fine. Version-Release number of selected component (if applicable): 6.2.0 Beta GA10.1 How reproducible: always Steps to Reproduce: 1. register a host to your satellite so it appears in Content Hosts 2. Try to put its hostname to the search field and hit search 3. check production.log Actual results: ISE Expected results: Search query is being validated performed on all applicable fields. Additional info: Workaround is to use the explicit-field search query: name = my-host-1.domain.org or name ~ my-host-1.domain.org - I'm requesting a blocker flag for this BZ as this will be hit quite often by users (single word search queries are the most commonly used)