Red Hat Bugzilla – Bug 437547
Query Parse error for package search when sat sync is running
Last modified: 2010-10-22 19:16:28 EDT
Description of problem:
Basically after you install a satellite, while sat sync is running, you goto
enter any search string you get a wierd error
* Could not parse query '<search_string>'."
Its just that the file has not been indexed yet, the actual error has nothing to
do with query parsing..
Version-Release number of selected component (if applicable): 5.1
How reproducible: Always
Steps to Reproduce:
1. Install satellite
2. Do not start the sat sync yet...
3. Logon to the UI
4. click on channels
5. click on Package search
6. Enter search string "perl" and click on search
You see error message ->
* Could not parse query 'perl'.
Some sort of message saying the search indexing is probably going on right now.
You might want to wait before starting the search.. In fact there could be a
warning message as soon as you click on the Package Search tab saying "Note:
Search Indexes have not be created, please try your search after a few minutes
or check with your system adminitstrator."
Fixed in this commit
Added a message that will display index files are missing instead of 'could not parse query'.
What was happening in this issue is no packages existed in the db, so there was nothing indexed, search-server had no index files to search and we weren't checking the exception type in the webui.
Note: We aren't adding a message to state if indexing is in progress or not. That's a more difficult problem to solve. In particular solving it for system search would be tricky. System search potentially searches several indexes. It's possible a given query will succeed and find data, while something like snapshots maybe won't find index files. Essentially, the answer of data being available or not is dependent on what query the user executes. I'd like to request we file a separate bz if this functionality is desired.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.