Bug 614529 - colon in resource name confuses the search
colon in resource name confuses the search
Status: CLOSED CURRENTRELEASE
Product: RHQ Project
Classification: Other
Component: SearchBar (Show other bugs)
3.0.0
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: Joseph Marques
Corey Welton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-14 12:53 EDT by Lukas Krejci
Modified: 2010-08-12 12:53 EDT (History)
1 user (show)

See Also:
Fixed In Version: 2.4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-12 12:53:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lukas Krejci 2010-07-14 12:53:03 EDT
Description of problem:

When a resource name contains a colon (a common thing), no results are displayed when searching for such resources with an error on the server console:

18:48:09,274 ERROR [STDERR] line 1:32 no viable alternative at character ':'
 
How reproducible:
always

Steps to Reproduce:
1. Inventory a JBoss AS or an Apache instance with a colon in its resource name
2. start typing name=", wait for the suggestion to offer you the name with a colon
2a. alternatively just type the resource name in the search box
3. Click "Go"
  
Actual results:
no results returned and an error on the server output.

Expected results:
the results should contain the searched for resource, no error in server console.
Comment 1 Joseph Marques 2010-07-15 10:50:05 EDT
commit bcd005aee3303e3cf230eb8e9a0595829f283b54
Author: Joseph Marques <joseph@redhat.com>
Date:   Thu Jul 15 10:48:42 2010 -0400

BZ-614529: support search expressions containing ':'
Comment 2 Corey Welton 2010-07-16 10:45:42 EDT
QA Verified, these search expressions now return appropriate results when selected.
Comment 3 Corey Welton 2010-08-12 12:53:30 EDT
Mass-closure of verified bugs against JON.

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