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 clicked on "Capsule" breadcrumb, it redirects to Capsule Overview instead it should capsule list should open.
Version-Release number of selected component (if applicable):
Satellite 6.8.0
How reproducible:
Always
Steps to Reproduce:
1. Install capsule
2. Infrastructure -> Capsule -> Open the installed capsule
3. Open any tab other than Overview. Click on Capsule breadcrumb
Actual results:
Overview page of the capsule opens up.
Expected results:
Capsule list page should open up.
Additional info:
Hi Akhil,
The resulting behavior is the same for all 3 bugzillas (i.e. redirect to overview); therefore, it is highly likely the same root cause (i.e. single bug fix). Any objection if we close bug 1856331 (this one) and bug 1856388 as duplicates of bug 1856370?
Yes it is highly likely that a single bug fix will resolve other bug as well. So, I don't have any objection on closing bug 1856331 (this one) and bug 1856388 as duplicates of bug 1856370.