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.
DescriptionStephen Wadeley
2021-03-18 15:59:11 UTC
Description of problem:
Version-Release number of selected component (if applicable):
Sat6.9 snap 17
Steps to Reproduce:
1. Create a product and repo with images (in this case, hello-world [1])
2. Create a Content View of the container images and publish it
3. On the CLI, login to Satellite Server: podman login --tls-verify=false
<sat6>
4. Create a CCV, add above CV, publish, promote to atest LCE
5. podman search --tls-verify=false <sat6>/default_organization
6. Try to pull all the images listed in the search step
Actual results:
I see some :
Requesting bear token: invalid status code from registry 500 (Internal Server Error)
Trying to pull dhcp-2-45/default_organization-pm_test-b-docker-docker-images-hello-world:latest...
Getting image source signatures
Copying blob b8dfde127a29 [--------------------------------------] 0.0b / 0.0b
Copying config d1165f2212 done
Writing manifest to image destination
Storing signatures
d1165f2212346b2bab48cb01c1e39ee8ad1be46b87873d9ca7a4e434980a7726
[sjw@t480s tmp]$ podman pull --tls-verify=false dhcp-2-45/default_organization-docker-images-3_0-docker-images-hello-world
Trying to pull dhcp-2-45/default_organization-docker-images-3_0-docker-images-hello-world:latest...
Requesting bear token: invalid status code from registry 500 (Internal Server Error)
Error: Error initializing source docker://dhcp-2-45/default_organization-docker-images-3_0-docker-images-hello-world:latest: Requesting bear token: invalid status code from registry 500 (Internal Server Error)
[sjw@t480s tmp]$ podman pull --tls-verify=false dhcp-2-45/default_organization-docker-images-hello-world
Trying to pull dhcp-2-45/default_organization-docker-images-hello-world:latest...
Getting image source signatures
Copying blob b8dfde127a29 [--------------------------------------] 0.0b / 0.0b
Copying config d1165f2212 done
Writing manifest to image destination
Storing signatures
d1165f2212346b2bab48cb01c1e39ee8ad1be46b87873d9ca7a4e434980a7726
[sjw@t480s tmp]$ podman pull --tls-verify=false dhcp-2-45/default_organization-docker-images-1_0-docker-images-hello-world
Trying to pull dhcp-2-45default_organization-docker-images-1_0-docker-images-hello-world:latest...
Requesting bear token: invalid status code from registry 500 (Internal Server Error)
Error: Error initializing source docker://dhcp-2-45/default_organization-docker-images-1_0-docker-images-hello-world:latest: Requesting bear token: invalid status code from registry 500 (Internal Server Error)
Expected results:
Either an image can be pulled or a meaningful error message is given
Additional info:
[1] https://hub.docker.com/_/hello-world
The root cause is that podman search returned versioned repos, but we don't support pulling them today. Technically you could have pulled via crane with pulp2, but they never got synced to capsules. I'm going to propose we do not return these in the search results.
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.10 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-2021:4702