Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJoniel Pasqualetto
2023-10-25 13:25:02 UTC
Description of problem:
There are 2 different issues that I believe are at play here.
1. Authentication during discovery is not really working not allowing the discovery of any repositories on private registriers.
2. If/when the query to the v2/_catalog works, the way we're dealing with the results returns nothing for the user at the webUI
Version-Release number of selected component (if applicable):
Satellite 6.13 where I tested but most likely also observed on previous versions
How reproducible:
Always
Steps to Reproduce:
1. Create a private registry that only supports api v2 (anything on azurecr.io, for example). I do have a reproducer for testing purposes I can share.
2. push some images to your private registry
3. try discovering the repositories
Actual results:
1. Discover always return 401 errors (using the right password)
2. If the registry is public, it simply returns no results
Expected results:
Be able to discover container repositories on v2 only registries
Be able to discover container repositories on private registries
Additional info:
I have a possible patch that worked on my lab. Will propose it upstream for discussion/validation.
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.15.0 release), 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-2024:2010