-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lack of pullsecret which cause S2I build from authenticated registry can't pull image #3335
Comments
/area system-pz |
I got the bug info here https://bugzilla.redhat.com/show_bug.cgi?id=1771335 |
Reopen this issue to add testcases releated to pull-secret error for upstream CI of s390x. |
@zhengxiaomei123 In 4.5 we have cluster-scoped secrets and is used globally. Before that every namespace had to have a secrets for all registries that will be used in the namespace. if your test needs to pull something from registry.redhat.io, it should have a secret for this registry. The pull secret from the installer should live in the openshift-config namespace as secret/pull-secret, if you want to reuse in another namespace, it should be copied to this namespace. So oc-import will throw error if you run your configuration script on < 4.5 cluster. I have a pr #3737 that solves the problem. You can have alook. |
@amitkrout This is coincident with what I tested. Thanks for your confirmation. |
/kind bug
What versions of software are you using?
Operating System:
Red Hat Enterprise Linux 8.2 (Ootpa)
Output of
odo version
:odo v1.2.2 (b815649)
How did you run odo exactly?
make test-cmd-cmp
Actual behavior
Expected behavior
In myproject , there is pullsecret with kind of dockerconfigjson
Any logs, error output, etc?
The text was updated successfully, but these errors were encountered: