Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Description of problem:
The /etc/containers/registries.conf file is not configured to search registry.access.redhat.com so UBI and RHEL image pulls fail without authentication. We need this "unauthenticated" registry available for UBI in particular.
Version-Release number of selected component (if applicable):
Version: 1.0.2-dev
Go Version: go1.11.5
OS/Arch: linux/amd64
How reproducible:
100%
Steps to Reproduce:
1. [root@rhel8 registries.d]# podman pull ubi8
Output:
2.
3.
Actual results:
Trying to pull registry.redhat.io/ubi8:latest...Failed
Trying to pull quay.io/ubi8:latest...Failed
Trying to pull docker.io/ubi8:latest...Failed
error pulling image "ubi8": unable to pull ubi8: 3 errors occurred:
* Error determining manifest MIME type for docker://registry.redhat.io/ubi8:latest: unable to retrieve auth token: invalid username/password
* Error determining manifest MIME type for docker://quay.io/ubi8:latest: Error reading manifest latest in quay.io/ubi8: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>404 Not Found</title>\n<h1>Not Found</h1>\n<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>\n"
* Error determining manifest MIME type for docker://ubi8:latest: Error reading manifest latest in docker.io/library/ubi8: errors:
denied: requested access to the resource is denied
unauthorized: authentication required
Expected results:
Find and pull the image and cache it locally like normal.
Additional info:
> The /etc/containers/registries.conf file is not configured to search registry.access.redhat.com
Isn't that registry deprecated? Why would we want to search it by default?
It was brought back from the Brink. UBI saved it. We force users of registry.redhat.io to have a Red Hat license to access it,
But registry.access.redhat.com is open to anyone.
Since we want everyone to use UBI, we need to leave it on an Open Registry.
Dan, is dead on. registry.redhat.io and registry.access.redhat.com are both backended by pulp, but moving to quay.io. Until registry.redhat.io moves to quay, we won't be able to support "unauthenticated" repositories for UBI. Even after we do eventually migrate (no timeline today), we will put redirects in place to make sure that registry.access.redhat.com doesn't break until the end of the RHEL 8 lifecycle. Where people get images from is sort of assumed to be part of the value prop of a long lifecycle of RHEL. AKA, people's stuff shouldn't break...
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, 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-2019:3403