Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Empty content searches for errata on a freshly installed system with nothing synced gave an index missing exception error. This fix corrects the content search controller and the error no longer appears.
Description of problem:
I suspect this only occurs on a system where errata in ANY org -- the testing one or otherwise -- have never been synced.
Version-Release number of selected component (if applicable):
Katello Version: 0.2.47-1.git.225.b3aa579.el6_3
How reproducible:
Steps to Reproduce:
1. Install a fresh system. Assure nothing is yet synced, particularly not RH repos. I also used --deployment=cfse but that might not matter.
2. Create/sync a Provider ("Google"), Product ("Google Chrome") and Repos ("x86_64", http://dl.google.com/linux/chrome/rpm/stable/x86_64) ("i386", http://dl.google.com/linux/chrome/rpm/stable/i386)
3. Content > Content Search
4. in the left-hand Browse pane, choose a dropdown of "Errata".
5. In the resulting "Repos" box, click to focus on the first search field.
6. Do not enter anything; click submit.
Actual results:
404 : {"error":"IndexMissingException[[katello_errata] missing]","status":404} (Tire::Search::SearchRequestFailed)
Click here for more details.
Expected results:
Presumably blank results.
Additional info:
Key here is that the errata search index did not exist. So to properly reproduce, no errata ever should have been synced in any organization.
e9bf154b5341e84820bc55a96994b7d6854980f6
will move to on_dev after merge to master.
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.
http://rhn.redhat.com/errata/RHSA-2012-1543.html
Description of problem: I suspect this only occurs on a system where errata in ANY org -- the testing one or otherwise -- have never been synced. Version-Release number of selected component (if applicable): Katello Version: 0.2.47-1.git.225.b3aa579.el6_3 How reproducible: Steps to Reproduce: 1. Install a fresh system. Assure nothing is yet synced, particularly not RH repos. I also used --deployment=cfse but that might not matter. 2. Create/sync a Provider ("Google"), Product ("Google Chrome") and Repos ("x86_64", http://dl.google.com/linux/chrome/rpm/stable/x86_64) ("i386", http://dl.google.com/linux/chrome/rpm/stable/i386) 3. Content > Content Search 4. in the left-hand Browse pane, choose a dropdown of "Errata". 5. In the resulting "Repos" box, click to focus on the first search field. 6. Do not enter anything; click submit. Actual results: 404 : {"error":"IndexMissingException[[katello_errata] missing]","status":404} (Tire::Search::SearchRequestFailed) Click here for more details. Expected results: Presumably blank results. Additional info: