Bug 746772 - Scoped Search - organization keyword throws error
Summary: Scoped Search - organization keyword throws error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Amos Benari
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-10-17 18:21 UTC by Eric Helms
Modified: 2019-09-26 13:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:01:41 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot (12.04 KB, image/png)
2012-02-01 04:42 UTC, Corey Welton
no flags Details

Description Eric Helms 2011-10-17 18:21:29 UTC
Description of problem:
When attempting to search on organization, as organization is typed into the filter box a request with the search parameters 'or' is issued and throws the following error.

undefined method `value' for :ScopedSearch::QueryLanguage::AST::LogicalOperatorNode

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


How reproducible:
Always

Steps to Reproduce:
1. Go to Organizations page
2. Click in search box
3. Type 'or'
  
Actual results:
Error notification - undefined method `value' for :ScopedSearch::QueryLanguage::AST::LogicalOperatorNode

Expected results:
No error message.

Additional info:

Comment 1 Amos Benari 2011-10-18 15:01:21 UTC
This is an auto-completer bug in scoped_search gem.
fixed upstream in commit #f00a18e8154074bc414d1fc48991aea1e3ea07bb

Comment 2 Mike McCune 2012-01-26 19:07:38 UTC
mass ON_QA move

Comment 4 Corey Welton 2012-02-01 04:42:33 UTC
Created attachment 558742 [details]
screenshot

Bouncing back to dev. That said, I'm not terribly concerned for this BZ, it can be moved off a blocker.

Comment 5 Corey Welton 2012-02-01 04:43:19 UTC
BTW, above was tested on Katello Version: 0.1.207-1.git.2.7881501.el6

Comment 6 Corey Welton 2012-02-01 04:43:54 UTC
uggh wrong bug sorry.  reopening.

Comment 7 Corey Welton 2012-02-10 13:39:20 UTC
This issue is mostly no longer applicable due to implementation of elasticsearch, but retested anyway in current build and issue no longer appears. QA Verified.

Comment 9 Mike McCune 2013-08-16 17:52:42 UTC
getting rid of 6.0.0 version since that doesn't exist


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