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.

Created attachment 1827500 [details]
Screenshot of the empty repository field

Description of problem:
When viewing the details page of a container image tag, the repository field is not filled in.

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

How reproducible:
100%

Steps to Reproduce:
1. Have a Satellite with a container image tag
2. Navigate to Content > Content Types > Container Image Tags
3. Confirm the tag has an associated repository under the 'Repository Name' column in the table
4. Click the tag's name to view its details

Actual results:
The 'Repository' field is blank

Expected results:
The 'Repository' field is populated with the associated repository.

Additional info:

Is this a regression from Satellite 6.9?

Confirmed regression in Sat 6.9.7 snap 1, following same steps as above.

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

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