Bug 2009069 - Repository not displayed in container image tag's details page
Summary: Repository not displayed in container image tag's details page
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management - Content
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.14.0
Assignee: Chris Roberts
QA Contact: Samir Jha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-29 20:21 UTC by Silas Pusateri
Modified: 2023-06-27 17:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot of the empty repository field (46.52 KB, image/png)
2021-09-29 20:21 UTC, Silas Pusateri 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35710 0 Normal New Docker tags, manifests, and manifest lists aren't displaying properly 2023-04-06 20:05:52 UTC
Github Katello katello pull 10533 0 None open Fixes #35710 - Update AngularJS Docker pages to display correctly 2023-04-26 20:31:03 UTC
Red Hat Issue Tracker SAT-17572 0 None None None 2023-05-08 10:56:30 UTC

Description Silas Pusateri 2021-09-29 20:21:11 UTC 
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:
Comment 1 Brad Buckingham 2021-09-30 14:07:47 UTC 
Is this a regression from Satellite 6.9?
Comment 2 Silas Pusateri 2021-10-06 18:49:54 UTC 
Confirmed regression in Sat 6.9.7 snap 1, following same steps as above.
Comment 3 Bryan Kearney 2023-05-04 00:02:02 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35710 has been resolved.
Note You need to log in before you can comment on or make changes to this bug.