Bug 2037180

Summary: Failed to docker pull image with "Error: image <image name> not found" error
Product: Red Hat Satellite Reporter: Hao Chang Yu <hyu>
Component: Container Management - ContentAssignee: Ryan Verdile <rverdile>
Status: CLOSED ERRATA QA Contact: addubey
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: ahumbe, iballou, pcreech, vijsingh
Target Milestone: 6.11.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: 2022-07-05 14:31:28 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 Hao Chang Yu 2022-01-05 07:02:40 UTC 
Description of problem:
After setting the "Unauthenticated Pull: Yes", it is not taking effect in Capsule until user performs a Complete Capsule sync. Publish/Promote a new version of CV won't help if no content is changed.

Steps to Reproduce:
1. Create and sync a container repo
2. Create a CV and add the container repo to it
3. Publish and Promote the CV and make sure Capsule sync is triggered.
4. Wait for the Capsule sync to finish
5. Go the the LCE page and set "Unauthenticated Pull: Yes".
6. From any host run docker pull

docker pull capsule.example.com/mycontainer:latest

Actual results:
Image not found error

# On Capsule:
# sqlite3 /var/lib/foreman-proxy/smart_proxy_container_gateway.db
sqlite> .header on
sqlite> select * from repositories;
id|name|auth_required
6|busybox|1 <============ should be 0


Expected results:
Refresh the database in the smart proxy container gateway immediately after setting the "Unauthenticated Pull", such as trigger a foreman-task to refresh the data.

Image can be pulled successfully from Capsule.
Comment 2 Bryan Kearney 2022-03-04 16:04:58 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34530 has been resolved.
Comment 6 errata-xmlrpc 2022-07-05 14:31:28 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 (Moderate: Satellite 6.11 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-2022:5498