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:

- Clicking on the container count link on the CV Repositories page redirects to an invalid page.

Version-Release number of selected component (if applicable):

- Satellite 6.13

How reproducible:

- Everytime.

Steps to Reproduce:

1. Sync a container repository on the Satellite.

2. Create a CV or use a existing CV.

3. Navigate to the Repositories page on the CV.

   Satellite WebUI : Content --> Content View --> Select CV --> Repositories tab --> Click on any of the link in Content column for the container repository.

Actual results:

- Redirected to an invalid page.

  ~~~
  404 - Page Not Found
  The requested URL /products/1/repositories/2/content/content/docker_manifests was not found.
  ~~~

Expected results:

- Should redirect to the correct page.

Additional info:

- Seems like the URL is generated incorrectly.

  https://satellite.example.com/products/1/repositories/2/content/content/docker_manifests 

  It should be the following instead.

  https://satellite.example.com/products/1/repositories/2/content/docker_manifests

Created redmine issue https://projects.theforeman.org/issues/36474 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36474 has been resolved.

Verified on Satellite 6.14 sn 6, repo content links are now correct for container repo in a CV UI

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 (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6818