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:
For all katello pages - on accessing invalid subpath (e.g. http://sat.server.com/activation_keys/foo) the URL redirect loop occurs finally resulting in ISE.
- after a brief investigation it looks like it's the bastion_katello.js library which is causing this.
-no errors in logs, only perfectly handled GET requests.
Version-Release number of selected component (if applicable):
6.1.8
6.2.0 Snap #4
How reproducible:
akways
Steps to Reproduce:
1. navigate to some katello page
2. add some invalid subpath, e.g. '/foo'
3. enojoy the perpetuum mobile
Actual results:
URL redirect loops happens overloading the server, resulting in ISE
Expected results:
HTTP/400 page as for Foreman pages
Additional info:
Yes, I think it is a duplicate of bug #1108783. I am going to close this as such and put bug #1108783 into 6.2.0.
*** This bug has been marked as a duplicate of bug 1108783 ***