-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.13.z, 4.12.z
-
Important
-
No
-
3
-
OSDOCS Sprint 236
-
1
-
False
-
Description of problem:
When a customer does not specify a --authfile /path/to/pull-secret.txt it is not possible to pull/build RHCOS images.
Version-Release number of selected component (if applicable):
4.12 (TP), 4.13
How reproducible:
Always.
Steps to Reproduce:
1. podman pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:13d7cff3fd3b59c6fdf35c76d283e9e31a2981210640677fd92475b345392352
Actual results:
Trying to pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:13d7cff3fd3b59c6fdf35c76d283e9e31a2981210640677fd92475b345392352... Error: initializing source docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:13d7cff3fd3b59c6fdf35c76d283e9e31a2981210640677fd92475b345392352: reading manifest sha256:13d7cff3fd3b59c6fdf35c76d283e9e31a2981210640677fd92475b345392352 in quay.io/openshift-release-dev/ocp-v4.0-art-dev: unauthorized: access to the requested resource is not authorized
Expected results:
podman pull --authfile pull-secret.txt quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:13d7cff3fd3b59c6fdf35c76d283e9e31a2981210640677fd92475b345392352 Trying to pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:13d7cff3fd3b59c6fdf35c76d283e9e31a2981210640677fd92475b345392352... Getting image source signatures Copying blob 34294461fe40 done [snipped] Writing manifest to image destination Storing signatures 79640b6f6fab4d06ccc43572151b2c65759c5ecbda39cdc06e5267bc032cddfa
Additional info:
Customer should be informed how to obtain the cluster pull-secret.