After synchronizing a repository and creating a filter, errors result when trying to search for packages starting with carets ("^"). This fix escapes the caret, which is can now be used for elastic searches.
DescriptionGarik Khachikyan
2012-04-23 10:39:28 UTC
Created attachment 579480[details]
error screen
Description of problem:
Red traceback happens when one tries to search for a package by starting to type "^" (having synced a content - custom repo is enough for reproducer)
Version-Release number of selected component (if applicable):
katello-glue-candlepin-0.1.309-1.el6.noarch
pulp-1.0.4-1.el6.noarch
qpid-cpp-client-ssl-0.12-6.el6.x86_64
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-common-0.1.107-1.el6.noarch
katello-cli-0.1.107-1.el6.noarch
pulp-common-1.0.4-1.el6.noarch
katello-glue-foreman-0.1.309-1.el6.noarch
qpid-cpp-server-0.12-6.el6.x86_64
pulp-selinux-server-1.0.4-1.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-agent-0.17-1.el6.noarch
katello-certs-tools-1.0.4-1.el6.noarch
katello-common-0.1.309-1.el6.noarch
candlepin-0.5.26-1.el6.noarch
qpid-cpp-client-0.12-6.el6.x86_64
katello-0.1.309-1.el6.noarch
katello-configure-0.1.107-1.el6.noarch
candlepin-tomcat6-0.5.26-1.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
m2crypto-0.21.1.pulp-7.el6.x86_64
python-oauth2-1.5.170-2.pulp.el6.noarch
katello-glue-pulp-0.1.309-1.el6.noarch
katello-selinux-0.1.10-1.el6.noarch
qpid-cpp-server-ssl-0.12-6.el6.x86_64
mod_wsgi-3.3-3.pulp.el6.x86_64
python-qpid-0.12-1.el6.noarch
python-isodate-0.4.4-4.pulp.el6.noarch
How reproducible:
always
Steps to Reproduce:
1.sync a repo (e.g. http://inecas.fedorapeople.org/fakerepos/zoo3/)
2.got to Filters page.
3.create a filter
4. type in "Add package" input: ^
Actual results:
traceback (see attached the screenshot)
Expected results:
no traceback(s)
Additional info:
Latest Katello as well has the same issue.
Attached is the screenshat
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.
http://rhn.redhat.com/errata/RHSA-2012-1543.html