-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
3
-
False
-
-
False
-
Konflux
-
-
-
Customer Reported
Summary from support thread:
When users create a pull secret by uploading a configuration file, we allow them to create a pull secret that doesn't work with our tasks. We should validate these inputs and prompt a user with a warning that they might need to use a different secret type. We could also add a warning in the Secrets page if we suspect there may be a validation issue with a pull secret.
Request type: Error / Bug
Reason of urgency: Build is continue failing
Request info
Team: crc
Tenant: https://konflux-ui.apps.stone-prod-p02.hjvn.p1.openshiftapps.com/ns/crc-tenant/applications/patched-image
Application: patched-image
Details:
pipeline is failing because of image pull secret is not correct
https://konflux-ui.apps.stone-prod-p02.hjvn.p1.openshiftapps.com/ns/crc-tenant/applications/patched-images/pipelineruns/cluster-kube-apiserver-operator-on-pull-request-2htp7 (https://konflux-ui.apps.stone-prod-p02.hjvn.p1.openshiftapps.com/ns/crc-tenant/applications/patched-image\[…\]apiserver-operator-on-pull-request-2htp7) is failing because of image registry auth failure but I tried to use same secret with podman and able to pull the image . I updated secret multiple time also but no success.
```$ podman pull --authfile /tmp/reg.json registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.23-openshift-4.19
Trying to pull registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.23-openshift-4.19...
Getting image source signatures
Copying blob c12a0543fd04 \[--------------------------------------\] 84.3KiB / 98.0MiB \| 1.6 MiB/s```
- links to
