Bug 2170125

Summary: Missing repository name (image name) in Container tags CVv comparison
Product: Red Hat Satellite Reporter: Radek Mynar <rmynar>
Component: Content ViewsAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Samir Jha <sajha>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: chrobert, pcreech, sajha, sbible
Target Milestone: 6.14.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:18:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
missing docker image name in content view version comparison none

Description Radek Mynar 2023-02-15 17:42:11 UTC
Created attachment 1944372 [details]
missing docker image name in content view version comparison

Description of problem:
Repository name (Image name) is not shown on Container tags tab of Content view version comparison

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

How reproducible:
always

Steps to Reproduce:
1. Create a product, create two or more different docker repositories, choose various tags in 'Include tags' (e.g. "latest, stable"), sync repositories
2. Create a Content view, add repositories created in previous step, publish two Content view versions
3. Compare the two Content view versions and go to "Container tags"

Actual results:
Only tags are visible, but it's not clear to which image the tags belong
(see screenshot)

Expected results:
Image name (Upstream repository name) should be shown

Additional info:
-

Comment 1 Samir Jha 2023-04-11 16:29:19 UTC
Created redmine issue https://projects.theforeman.org/issues/36290 from this bug

Comment 6 errata-xmlrpc 2023-11-08 14:18:30 UTC
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