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.
Bug 1530280 - Docker Tags link on repository details page points to Docker Manifests
Summary: Docker Tags link on repository details page points to Docker Manifests
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.4.0
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-02 12:40 UTC by Peter Ondrejka
Modified: 2019-11-05 23:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:09:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
verification screenshot (23.84 KB, image/png)
2018-05-31 17:21 UTC, jcallaha
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22998 0 None None None 2018-03-22 18:36:40 UTC

Description Peter Ondrejka 2018-01-02 12:40:41 UTC
Description of problem:

In Sat 6.3 UI, on docker repository details page, clicking on the number next to Docker Tags in the Content Counts table leads to docker manifests page of the repo (.../products/1/repositories/1/content/content/docker_manifests?page=1&per_page=20)

Version-Release number of selected component (if applicable):
Satellite 6.3 snap 30

How reproducible:
Always

Steps to Reproduce:
1. Create and sync a docker repository with some tags, e.g. using steps from https://bugzilla.redhat.com/show_bug.cgi?id=1513854#c4
2. Navigate to the repository link and click the link (number) next to Docker Tags 

Actual results:

Points to docker manifests page

Expected results:

Should list docker tags associated with the repo

Additional info:

Comment 2 Brad Buckingham 2018-03-19 20:51:02 UTC
Note: the same behavior is observed by:

- create a product
- create a docker repo
- sync docker repo

- go to Content -> Products -> [docker product] -> Repositories : click the 'N Docker Tags' link

- go to Content -> Products -> [docker product] -> Repositories -> [docker repo] -> click the N associated with 'Docker Tags'

Comment 3 Brad Buckingham 2018-03-22 18:36:38 UTC
Created redmine issue http://projects.theforeman.org/issues/22998 from this bug

Comment 5 Satellite Program 2018-04-03 18:18:28 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22998 has been resolved.

Comment 6 jcallaha 2018-05-31 17:21:01 UTC
verified in Satellite 6.4 Snap 5.

After syncing the docker repo, i see that the tag link looks correct:
https://<mysat>/products/45/repositories/75/content/content/docker_tags

Clicking through the link brings me to a correct tags page.

See screenshot for verification.

Comment 7 jcallaha 2018-05-31 17:21:27 UTC
Created attachment 1446360 [details]
verification screenshot

Comment 8 Bryan Kearney 2018-10-16 19:09:23 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:2927


Note You need to log in before you can comment on or make changes to this bug.