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 2254408 - Unable to sync library/busybox from gcr.io
Summary: Unable to sync library/busybox from gcr.io
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.15.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.15.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-13 19:17 UTC by Vladimír Sedmík
Modified: 2024-04-23 17:16 UTC (History)
9 users (show)

Fixed In Version: pulp-container-2.16.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2262131 2265149 (view as bug list)
Environment:
Last Closed: 2024-04-23 17:16:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp_container issues 1444 0 None closed Cannot sync library/busybox because of unsupported mediatype "manifest.v1+prettyjws" 2023-12-13 21:07:20 UTC
Red Hat Issue Tracker SAT-21883 0 None None None 2023-12-13 19:19:01 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:16:20 UTC

Description Vladimír Sedmík 2023-12-13 19:17:27 UTC
Description of problem:
In 6.15.0 we are not able to sync library/busybox from mirror.gcr.io
The same works well in 6.14.1 (python39-pulpcore-3.22.19-1.el8pc.noarch.rpm, python39-pulp-container-2.14.7-1.el8pc.noarch.rpm) and earlier.


Version-Release number of selected component (if applicable):
6.15.0 (python3.11-pulpcore-3.39.2-2.el8pc.noarch.rpm, python3.11-pulp-container-2.16.2-2.el8pc.noarch.rpm)


How reproducible:
always


Steps to Reproduce:
1. Create a docker repo and try to sync library/busybox from mirror.gcr.io


Actual results:
Sync task fails with
404, message='Not Found', url=URL('https://mirror.gcr.io/v2/library/busybox/manifests/1.24')

even though the URL is available and serves a schema 1 manifest


Expected results:
Successful sync

Comment 3 Robin Chan 2023-12-13 21:07:22 UTC
The Pulp upstream bug status is at closed. Updating the external tracker on this bug.

Comment 4 Robin Chan 2023-12-13 21:07:24 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 5 lmjachky 2023-12-15 07:49:52 UTC
The fix was shipped in https://github.com/pulp/pulp_container/releases/tag/2.16.3. Please, verify this pulp-container version.

Comment 6 Vladimír Sedmík 2024-01-16 08:56:42 UTC
Verified in 6.15.0 snap 5 (with python3.11-pulp-container-2.16.3-1.el8pc.noarch) - the repo can be sucessfully synced now.

Comment 9 errata-xmlrpc 2024-04-23 17:16:19 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


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