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.
Bug 1325799 - scoped_search - auto complete not working for Capsules page
Summary: scoped_search - auto complete not working for Capsules page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Shlomi Zadok
QA Contact: Roman Plevka
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-11 08:46 UTC by Roman Plevka
Modified: 2019-09-26 16:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:04:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14743 0 None None None 2016-04-22 14:58:59 UTC

Description Roman Plevka 2016-04-11 08:46:15 UTC 
Description of problem:
getting 404 for https://<sat6.server>/smart_proxies/auto_complete_search?search=

Version-Release number of selected component (if applicable):
6.2.0 Sanp 7.1
- this might have something to do with renaming smart proxies to capsules

foreman/production.log:

2016-04-11 10:45:31 [app] [I] Processing by SmartProxiesController#show as JSON
2016-04-11 10:45:31 [app] [I]   Parameters: {"search"=>"foo", "id"=>"auto_complete_search"}
2016-04-11 10:45:31 [app] [I]   Rendered common/404.html.erb within layouts/application (0.8ms)
2016-04-11 10:45:31 [app] [I]   Rendered layouts/_application_content.html.erb (0.2ms)
2016-04-11 10:45:31 [app] [I]   Rendered layouts/base.html.erb (0.7ms)
2016-04-11 10:45:31 [app] [I] Completed 404 Not Found in 15ms (Views: 2.6ms | ActiveRecord: 2.0ms)


How reproducible:
always

Steps to Reproduce:
1. navigate to Capsules page
2. start typing a query into a search bar
3. notice no suggestions appear, 404 in the browser console

Actual results:
404 for auto_complete url

Expected results:
auto complete works

Additional info:
Comment 2 Shlomi Zadok 2016-04-20 00:41:12 UTC 
Seems to be working on upstream Foreman (both 1.11 & develop).
Comment 3 Shlomi Zadok 2016-04-20 00:46:03 UTC 
Also, seems like not /proxies specific error.
It happens also in /compute_profiles.
Comment 4 Shlomi Zadok 2016-04-21 09:00:34 UTC 
Created redmine issue http://projects.theforeman.org/issues/14743 from this bug
Comment 5 Bryan Kearney 2016-04-21 14:06:23 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14743 has been closed
-------------
Shlomi Zadok
Applied in changeset commit:katello|fcbc603bd23bb317905b442ca4650fd619fcc2cf.
Comment 6 Roman Plevka 2016-05-06 12:31:05 UTC 
VERIFIED
on sat6.2.0 GA10
Autocomplete works great now, no errors in the console (getting status code 200)
Comment 7 Bryan Kearney 2016-07-27 11:04:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.