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.
Is there is a reproducer? This error should not be seen during sync as long as manifest lists that are being served from RH registry do not contain reference for schema1 digest.
Created attachment 1938365[details]
Hotfix RPM for Satellite 6.11.4
INSTALL INSTRUCTIONS:
1. Take a complete backup or snapshot of Satellite 6.11.4 server
2. Download the hotfix RPM matching your Satellite and RHEL version and copy it to Satellite server
3. # yum install ./tfm-pulpcore-python3-pulp-container-2.9.2-2.HOTFIXRHBZ2115970.el7pc.noarch.rpm --disableplugin=foreman-protector
4. # satellite-maintain service restart
Created attachment 1938366[details]
Hotfix RPM for Satellite 6.11.4 on RHEL8
INSTALL INSTRUCTIONS:
1. Take a complete backup or snapshot of Satellite 6.11.4 server on RHEL8
2. Download the hotfix RPM matching your Satellite and RHEL version and copy it to Satellite server
3. # dnf install ./python38-pulp-container-2.9.2-2.HOTFIXRHBZ2115970.el8pc.noarch.rpm --disableplugin=foreman-protector
4. # satellite-maintain service restart
Created attachment 1941448[details]
Hotfix RPM for Satellite 6.10.7
INSTALL INSTRUCTIONS:
1. Take a complete backup or snapshot of Satellite 6.10.7 server
2. Download the hotfix RPM matching your Satellite and RHEL version and copy it to Satellite server
3. # yum install ./python3-pulp-container-2.8.4-0.2.HOTFIXRHBZ2115970.el7pc.noarch.rpm --disableplugin=foreman-protector
4. # satellite-maintain service restart
Verified on 6.13 - Snap 12
Steps to Reproduce:
This issue wasn't able to be reliably reproduced, due to issues mentioned in comments above.
However, in this version of Satellite, the pulp container has been updated to include the fix(2.14 on satellite, fixed in 2.9.7), and in comments above this fix
did seem to resolve the issue.
Verifying this based on those pieces of information.
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.13 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-2023:2097
Description of problem: Sync container images of existing docker type repositories fail with 404 - Not found. The Satellite was upgrade from 6.9 -> 6.10 -> 6.11 Steps to Reproduce: 1. Go to an existing docker type repository 2. Hit the sync button 3. And the task fails with 404 - Not found Actual results: Sync fails with: --- 404, message='Not Found', url=URL('https://registry.redhat.io/containers/content/dist/containers/rhel8/multiarch/containers/redhat-rhosp-rhel8-openstack-aodh-api/manifests/1/sha256:2881fb630130572a95d370ba801fec3340d6738c001abcab8d70bfc063ad9cd2?_auth_=exp=1659560550~hmac=caae5ac4009b16a60c419da47fca4713362f5a3c24f6f6d6f288476a31f96161') --- Expected results: Sync should finish with success. Additional info: We observed that on a Satellite 6.9, syncing the same repository(URL Registry/URL Repository), it works. Also, creating an new repository on the Satellite 6.11 with the same URL Registry/URL Repository the sync works as expected. Not sure if the Satellite is being affected by this change -> https://access.redhat.com/articles/6138332