Bug 1093151 - search fails when searching 'foreman'
Summary: search fails when searching 'foreman'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: jmagen@redhat.com
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-30 18:02 UTC by Shannon Hughes
Modified: 2019-09-26 18:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:20:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log from student desktop for summit lab (38.76 KB, text/plain)
2014-04-30 18:08 UTC, Shannon Hughes
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5566 0 None None None 2016-04-22 16:17:04 UTC

Description Shannon Hughes 2014-04-30 18:02:10 UTC
Description of problem:
Go to the Monitor tab, then Facts

In the search box search for 'foreman' and we see a 500

url of response is https://192.168.100.50/fact_values?utf8=%E2%9C%93&search=foreman

Error is 

Warning!
PGError: ERROR: syntax error at or near "OR" LINE 1: ...an%' OR "fact_names"."name" ILIKE '%foreman%' OR OR "hostgr... ^ : SELECT DISTINCT "fact_values".id, "fact_values"."value" AS alias_0 FROM "fact_values" LEFT OUTER JOIN "fact_names" ON "fact_names"."id" = "fact_values"."fact_name_id" LEFT OUTER JOIN "hosts" ON "hosts"."id" = "fact_values"."host_id" AND "hosts"."type" IN ('Host::Managed') LEFT OUTER JOIN "hostgroups" ON "hostgroups"."id" = "hosts"."hostgroup_id" LEFT OUTER JOIN "hosts" "hosts_fact_values" ON "hosts_fact_values"."id" = "fact_values"."host_id" AND "hosts_fact_values"."type" IN ('Host::Managed') INNER JOIN "fact_names" fact_names_474344 ON (fact_names_474344.id = fact_values.fact_name_id) WHERE (fact_names.name <> '_timestamp') AND ((fact_names_474344."name" = '') AND ("fact_values"."value" ILIKE '%foreman%' OR "fact_values"."value" ILIKE '%foreman%' OR "fact_names"."name" ILIKE '%foreman%' OR OR "hostgroups"."name" ILIKE '%foreman%' OR "fact_names"."short_name" ILIKE '%foreman%')) ORDER BY "fact_values"."value" ASC NULLS FIRST LIMIT 20 OFFSET 0

Looks like building the query out we have two 'OR's: 

'%foreman%' OR "fact_values"."value" ILIKE '%foreman%' OR "fact_names"."name" ILIKE '%foreman%' OR OR "hostgroups"."name" ILIKE 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Shannon Hughes 2014-04-30 18:08:19 UTC
Created attachment 891268 [details]
log from student desktop for summit lab

Comment 3 RHEL Program Management 2014-04-30 18:27:18 UTC
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.

Comment 5 jmagen@redhat.com 2014-06-08 09:19:14 UTC
https://github.com/theforeman/foreman/pull/1500

Comment 6 Bryan Kearney 2014-06-19 14:02:56 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/5566 has been closed

Comment 9 sthirugn@redhat.com 2014-08-11 19:56:56 UTC
Verified.  When I searched for 'foreman' I got 'No entries found' and not Internal Server Error.

Version Tested:
GA Snap 4 - Satellite-6.0.4-RHEL-6-20140806.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.19-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.19-1.el6_5.noarch
* candlepin-tomcat6-0.9.19-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.6.0.38-1.el6sat.noarch
* foreman-compute-1.6.0.38-1.el6sat.noarch
* foreman-gce-1.6.0.38-1.el6sat.noarch
* foreman-libvirt-1.6.0.38-1.el6sat.noarch
* foreman-ovirt-1.6.0.38-1.el6sat.noarch
* foreman-postgresql-1.6.0.38-1.el6sat.noarch
* foreman-proxy-1.6.0.23-1.el6sat.noarch
* foreman-selinux-1.6.0.4-1.el6sat.noarch
* foreman-vmware-1.6.0.38-1.el6sat.noarch
* katello-1.5.0-28.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.57-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-3.el6sat.noarch
* pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch
* pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch
* pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-selinux-2.4.0-0.30.beta.el6sat.noarch
* pulp-server-2.4.0-0.30.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
* sssd-ldap-1.11.5.1-3.el6.x86_64

Comment 10 Bryan Kearney 2014-09-11 12:20:04 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


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