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.
Description of problem:
When clicking through to package count/view for a repo, user is taken to what is basically a content search page. On this page is a "Back to Results" button. This button is out of context for this workflow (since user did not get here from a standard content search) and causes infinite cursor.
Version-Release number of selected component (if applicable):
katello 1.4.6-15.el6sat
How reproducible:
Steps to Reproduce:
1. Create a provider, product, repo and upload some RPMs to it.
2. Navigate to Content > Repositories > Products > $product_name
3. On the ensuing product view page, click $product_name and click the number representing package count on that page. OR just click the package count that exists on the main view itself.
4. On the ensuing content view page, note the 'Back to Results' button
5. Click button once, then twice.
Actual results:
Upon clicking, contents are cleared; upon clicking again, user gets an infinite spinner.
Expected results:
I'm not sure how to best handle this, but this button makes no sense, contextually, when a user gets here from this path. If a user is using content search and gets to such a result, it makes sense, but when navigating in via a product/repo view, it does not.
Additional info:
(In reply to Walden Raines from comment #2)
> This was filed before the bastion rewrite of these pages. Please check to
> see if this is still applicable.
Just kidding, wrong bug.