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.

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:

This is an auto-completer bug in scoped_search gem.
fixed upstream in commit #f00a18e8154074bc414d1fc48991aea1e3ea07bb

mass ON_QA move

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.

BTW, above was tested on Katello Version: 0.1.207-1.git.2.7881501.el6

uggh wrong bug sorry.  reopening.

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.

getting rid of 6.0.0 version since that doesn't exist