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.
DescriptionCalvin Hartwell
2016-10-17 20:47:30 UTC
Description of problem:
The search field on the host page throws a SQL exception when typing in a simple string. If a correct string is entered, I.E name = somehostname the field works, but otherwise it doesn't.
For example: https://sat6fqdn/hosts?utf8=%E2%9C%93&search=abc
Throws the exception:
Oops, we're sorry but something went wrong ERROR: invalid reference to FROM-clause entry for table "smart_proxies" LINE 1: SELECT smart_proxies.id FROM "smart_proxies" "puppet_ca_prox... ^ HINT: Perhaps you meant to reference the table alias "puppet_ca_proxies_hosts".
Version-Release number of selected component (if applicable):
6.2.1
How reproducible:
100% reproducible
Steps to Reproduce:
1. Go to hosts page
2. Put in search term
3. Throws exception
Actual results:
Search by throws an exception
Expected results:
Search should not throw an exception but should give an empty search result or warning.
Additional info:
Is this even tested?!