-
Notifications
You must be signed in to change notification settings - Fork 66
Failed to pull image : rpc error: code = Unknown desc = unauthorized: authentication required #2980
Comments
The image is really there in the registry. When I create the app manually in
And the app in ppalaga-jenkins ns works as expected: http://wildfly-camel-example-camel-cdi-ppalaga-jenkins.8a09.starter-us-east-2.openshiftapps.com/ |
It works when I do the same steps with the spring-boot quickstart. I wonder where is the difference. |
I tried the above steps. I can reproduce the issue. Here the jenkins build is passed but I didn't found any deployed application on stage. On further investigation I found the image is built and pushed the problem occurs while deploying the application. While deploying it failed to access freshly built image from internal docker registry. For boosters it's working fine. I am not sure if it is a issue with this repo or with deployment of the application. Here is the image for openshift console: |
@piyush1594 Could you please check from the build side why docker image is not pushed into the docker registry though build pipeline is getting succeeded in the OSIO. |
@animuk from what is shown in the #2980 (comment) comment above, I think we can conclude that the image is pushed to the internal registry successfully. The image is there, only deployer cannot access it for some reason. |
I have a microservice deployment that consists of 11 images. I ran into this same error with OCP v3.9.27 when I changed the remote registry for the images. Imagestream, dc, rc, pod description all looked fine, the image in the new registry (ACR) was referenced in each place (I eyeballed the SHA265 hashes). Also I'm sure all 11 components successfully pushed into ACR. Somehow 1 of the 11 components refused to deploy with this same "failed to pull image: authentication required" error. Scaling the dc to 0 and back to 1 nor deleting pods helped. I fixed this for myself by starting fresh (imagestream remains unchanged to keep history data): The Image I was trying to pull was just some custom specific Java/SpringBoot application. |
Is this causing issues like the one below ?
|
Sorry, my problem was that I was just confused with RBAC. While I had created a service account and linked the ACR pull secret with it, my deployment config specifies no service account, so "normal" operations (such as oc rollout latest dc/mydc) are done with the default SA. Linked the external registry pull secret to default SA as well and now pulling works always, not just the first time. |
@giacomolm I have your issue very very frequently on Have you told openshit maintainers about this? |
I am also having this issue with a fresh |
Hi @Oliboy50 @theangrydev |
This is more of OpenShift issue. Removing tag from build team. |
Just face this same issue. |
I can see this problem in our periodic jobs today too. Job runs with user provisioned on |
+1 |
In my case it was an error in my buildconfig. I had to fix / remove an invalid image pull secret reference in the yaml. |
I just inserted the |
Experienced same issue just after upgrade oc 3.9 to 3.11. Root cause was oc client version discrepancy. After 3.11 upgrade , I forget to upgrade my oc client version. with old oc client I have created new project namespace. In there I experience same issue. Then I delete the project and upgrade the oc client version to 3.11 after that issue went away. |
On a freshly reset OSIO account, and tenant:
issue2980
:spa2
Expected: the deployment in stage namespace should succeed
Actual: the deployment in stage namespace does not succeed. As far as I can understand, the image cannot be pulled from the internal registry - see the
Failed to pull image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:39b9ea0bf18b480c850e46970981ff29b682d156f8475626a4697629b1b8034e": rpc error: code = Unknown desc = unauthorized: authentication required
event:The text was updated successfully, but these errors were encountered: