Bug 1481953

Summary: Browsing capsule puppet environments, clicking on 'number of classes' leads to 'Oops something went wrong"
Product: Red Hat Satellite Reporter: Ranjan Kumar <rankumar>
Component: SearchAssignee: Walden Raines <walden>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.10CC: bbuckingham, tbrisker, walden
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-13 16:30:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ranjan Kumar 2017-08-16 06:59:04 UTC
Description of problem: Browsing capsule puppet environments, clicking on 'number of classes' leads to 'Oops something went wrong"

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

How reproducible: Always

Steps to Reproduce:
1. In Satellite, navigate to Infrastructure -> Capsules
2. Click on a Capsule name
3. Select the Puppet tab
4. Select the Environments sub tab
5. Click on any of the numbers in the "Number of classes" column

Actual results: 

Oops, we're sorry but something went wrong Field 'environment+' not recognized for searching!

Production Log:
2017-08-16 17:56:55 235c4bc8 [app] [I] Started GET "/puppetclasses?search=environment%2B%3D%2Bexample_env" for 10.76.0.34 at 2017-08-16 17:56:55 +0530
2017-08-16 17:56:55 235c4bc8 [app] [I] Processing by PuppetclassesController#index as HTML
2017-08-16 17:56:55 235c4bc8 [app] [I]   Parameters: {"search"=>"environment+=+example_env"}
2017-08-16 17:56:55 235c4bc8 [app] [D] Setting current user thread-local variable to admin
2017-08-16 17:56:55 235c4bc8 [app] [D] Setting current organization thread-local variable to Redhat
2017-08-16 17:56:55 235c4bc8 [app] [D] Setting current location thread-local variable to none
2017-08-16 17:56:55 235c4bc8 [app] [W] Action failed
 | ScopedSearch::QueryNotSupported: Field 'environment+' not recognized for searching!
 | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/query_builder.rb:467:in `to_single_field_sql'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/query_builder.rb:480:in `to_sql'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/query_builder.rb:51:in `build_find_params'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/query_builder.rb:22:in `build_query'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/definition.rb:255:in `block in register_named_scope!'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/scoping/named.rb:151:in `call'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/scoping/named.rb:151:in `block (2 levels) in scope'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation.rb:285:in `scoping'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/scoping/named.rb:151:in `block in scope'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation/delegation.rb:70:in `block in search_for'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation.rb:285:in `scoping'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation/delegation.rb:70:in `search_for'
 | /usr/share/foreman/app/controllers/puppetclasses_controller.rb:8:in `index'

Expected results: should list the puppet classes 


Additional info:

Comment 7 Walden Raines 2017-09-13 16:30:17 UTC
I cannot reproduce this in satellite 6.3.0, I think this is likely a duplicate of bug #1408555.  Please reopen if you are able to reproduce this on Satellite 6.3.0.

*** This bug has been marked as a duplicate of bug 1408555 ***