Bug 2246121

Summary: Cannot discovery container repositories on private registries or on registries that only support api v2
Product: Red Hat Satellite Reporter: Joniel Pasqualetto <jpasqual>
Component: RepositoriesAssignee: Joniel Pasqualetto <jpasqual>
Status: CLOSED ERRATA QA Contact: Cole Higgins <chiggins>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.13.5CC: ahumbe, chiggins, chrobert, iballou, mkalyat, paji, rlavi, wpinheir
Target Milestone: 6.15.0Keywords: Triaged
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: 2024-04-23 17:15:27 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:

Description Joniel 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.
Comment 5 Chris Roberts 2023-11-01 17:40:38 UTC 
1st redmine is https://projects.theforeman.org/issues/36678
Comment 6 Bryan Kearney 2023-11-09 20:02:49 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36861 has been resolved.
Comment 11 errata-xmlrpc 2024-04-23 17:15: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 (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