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 1115316 - searching for partial product name is not functional
Summary: searching for partial product name is not functional
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-02 08:10 UTC by Jan Hutař
Modified: 2014-07-24 13:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-24 13:27:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Hutař 2014-07-02 08:10:29 UTC 
Description of problem:
Searching for partial product name is not functional


Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140626.1


How reproducible:
always


Steps to Reproduce:
1. Create a custom product "RHEL" and repository in it
2. Sync Red Hat repo "Red Hat Enterprise Linux Server"
3. Try to search custom product:
   Content -> Products -> search: "RHE" (missing "L")
4. Try to search Red Hat product:
   Content -> Products -> search: "Red" (missing majority of name)


Actual results:
No product is shown


Expected results:
In both cases products should be filtered as it seems more useful behavior


Additional info:
==> /var/log/foreman/production.log <==
Processing by Katello::Api::V2::ProductsController#index as JSON
  Parameters: {"enabled"=>"true", "organization_id"=>"1", "page"=>"1", "paged"=>"true", "search"=>"Red", "sort_by"=>"name", "sort_order"=>"ASC", "api_version"=>"v2"}
  Rendered /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/views/katello/api/v2/products/index.json.rabl within katello/api/v2/layouts/collection (3.5ms)
Completed 200 OK in 44ms (Views: 5.3ms | ActiveRecord: 2.0ms)
Comment 1 Jan Hutař 2014-07-02 08:11:06 UTC 
Also reported possibly related bug 1115315
Comment 3 David Davis 2014-07-22 17:44:12 UTC 
We've always used Lucene syntax which requires wildcards. So in your case, you'd search by RHE* or Red*.

That said, it's not apparent how to do partial searches so I think we should at least include some search information in the UI. I've created a bug for this:

https://bugzilla.redhat.com/show_bug.cgi?id=1122185
Comment 4 Jan Hutař 2014-07-22 20:41:34 UTC 
Hello. This way it is not consistent with rest of the product. E.g. when you use "RHE" to search through provisioning templates, one of templates you will get is "Kickstart RHEL default". I do understand that we are touching Katello vs. Foreman difference, but for Satellite product I do expect consistent behavior.
Comment 5 David Davis 2014-07-24 13:27:01 UTC 
Jan, that's one of the options I outline in https://bugzilla.redhat.com/show_bug.cgi?id=1122185#c3.
Note You need to log in before you can comment on or make changes to this bug.