Bug 1506403

Summary:	wrong docker tag id referenced in repository manage manifests page
Product:	Red Hat Satellite	Reporter:	Partha Aji <paji>
Component:	Container Management	Assignee:	Partha Aji <paji>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bbuckingham, egolov, sgraessl
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-katello-3.4.5.29	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 17:05:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Partha Aji 2017-10-25 22:34:48 UTC

1) Sync a docker repo
2) Go to Repository Details of that Repo and click on the number next to the manifest
3) Click on a tag name that shows up in the list. 
Note that you either get a message along the lines of "Can't find resource class: ::Katello::DockerMetaTag" or it points totally to the wrong tag.

In my example when I asked it to check show me information for Tag "1.24.1-musl" it instead highlighted information for "1.21-ubuntu".

Comment 1 Partha Aji 2017-10-25 22:34:53 UTC

Created from redmine issue http://projects.theforeman.org/issues/21470

Comment 2 Partha Aji 2017-10-25 22:34:57 UTC

Upstream bug assigned to paji

Comment 4 Satellite Program 2017-10-27 00:02:00 UTC

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

Comment 5 Peter Ondrejka 2017-11-27 11:51:10 UTC

Verified on Sat 6.3 snap 26, tag link in the repo's manifests table now points to correct location.

Comment 6 Bryan Kearney 2018-02-21 17:05:27 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, 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-2018:0336