Skip to content
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

Closed
zhengxiaomei123 opened this issue Jun 10, 2020 · 5 comments · Fixed by #3716
Closed
Labels
area/System-PZ Issues related to IBM System Z and System P kind/bug Categorizes issue or PR as related to a bug.

Comments

@zhengxiaomei123
Copy link
Contributor

/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?

[odo] Cloning "https://github.com/openshift/nodejs-ex" ...
[odo]         Commit:        a096bd299d65517cef8079f4559e9b0b9f97ff57 (Merge pull request #237 from bparees/nodejs12)
[odo]         Author:        Honza Horak <hhorak@redhat.com>
[odo]         Date:        Tue Mar 3 16:35:01 2020 +0100
[odo] Caching blobs under "/var/cache/blobs".
[odo] Warning: Pull failed, retrying in 5s ...
[odo] Warning: Pull failed, retrying in 5s ...
[odo] Warning: Pull failed, retrying in 5s ...
[odo] error: build error: After retrying 2 times, Pull image still failed due to error: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
[odo] I0609 12:22:04.392396  492873 occlient.go:1768] Status of cmp-git-testing-1 build is Running
[odo] I0609 12:22:04.393080  492873 occlient.go:1768] Status of cmp-git-testing-1 build is Running
[odo] I0609 12:22:04.393092  492873 occlient.go:1768] Status of cmp-git-testing-1 build is Failed
[odo]  ✗  Waiting for build to finish [53s]
[odo]  ✗  Failed to create component with name cmp-git. Please use `odo config view` to view settings used to create component. Error: failed to build component with args {Name:cmp-git SourcePath:https://github.com/openshift/nodejs-ex SourceRef: SourceType:git ImageName:nodejs EnvVars:[DEBUG_PORT=5858] Ports:[8080/TCP] Resources:&ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},} ApplicationName:testing Wait:true StorageToBeMounted:map[] StdOut:0xc000010018}: unable to build cmp-git-testing-1, error: : build cmp-git-testing-1 status Failed
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 10, 2020
@zhengxiaomei123
Copy link
Contributor Author

/area system-pz

@openshift-ci-robot openshift-ci-robot added the area/System-PZ Issues related to IBM System Z and System P label Jul 8, 2020
@zhengxiaomei123
Copy link
Contributor Author

I got the bug info here https://bugzilla.redhat.com/show_bug.cgi?id=1771335
the problem described in this issue has be resolved in the advisory :https://access.redhat.com/errata/RHBA-2020:0062
BTW , I tested on OCP Z 4.5-nightly-build. I will close the issue.

@zhengxiaomei123
Copy link
Contributor Author

Reopen this issue to add testcases releated to pull-secret error for upstream CI of s390x.

@amitkrout
Copy link
Contributor

@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.

@zhengxiaomei123
Copy link
Contributor Author

zhengxiaomei123 commented Aug 12, 2020

In 4.5 we have cluster-scoped secrets and is used globally.

@amitkrout This is coincident with what I tested. Thanks for your confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/System-PZ Issues related to IBM System Z and System P kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants