Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Failed to pull image : rpc error: code = Unknown desc = unauthorized: authentication required #2980

Open
ppalaga opened this issue Apr 10, 2018 · 18 comments

Comments

@ppalaga
Copy link
Contributor

ppalaga commented Apr 10, 2018

On a freshly reset OSIO account, and tenant:

git remote add ppalaga https://github.com/ppalaga/wildfly-camel-example-camel-cdi.git
git checkout master
git reset --hard issue2980
git push origin master -f
  • Create a new space called spa2
  • Import your fork as existing code, using just the three steps staging pipeline
  • Leaving override pom and Jenkinsfile should not change anything in the repo
  • The build should succeed

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:

LASTSEEN   FIRSTSEEN   COUNT     NAME                                        KIND                    SUBOBJECT                                          TYPE      REASON                           SOURCE                                                 MESSAGE
23m        23m         1         wildfly-camel-example-camel-cdi-1-7cd9s     Pod                                                                        Normal    Scheduled                        default-scheduler                                      Successfully assigned wildfly-camel-example-camel-cdi-1-7cd9s to ip-172-31-68-204.us-east-2.compute.internal
23m        23m         1         wildfly-camel-example-camel-cdi-1-7cd9s     Pod                                                                        Normal    SuccessfulMountVolume            kubelet, ip-172-31-68-204.us-east-2.compute.internal   MountVolume.SetUp succeeded for volume "default-token-9dl71" 
23m        23m         2         wildfly-camel-example-camel-cdi-1-7cd9s     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Normal    Pulling                          kubelet, ip-172-31-68-204.us-east-2.compute.internal   pulling image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:39b9ea0bf18b480c850e46970981ff29b682d156f8475626a4697629b1b8034e"
23m        23m         2         wildfly-camel-example-camel-cdi-1-7cd9s     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-68-204.us-east-2.compute.internal   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
23m        23m         2         wildfly-camel-example-camel-cdi-1-7cd9s     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-68-204.us-east-2.compute.internal   Error: ErrImagePull
23m        23m         7         wildfly-camel-example-camel-cdi-1-7cd9s     Pod                                                                        Normal    SandboxChanged                   kubelet, ip-172-31-68-204.us-east-2.compute.internal   Pod sandbox changed, it will be killed and re-created.
13m        23m         100       wildfly-camel-example-camel-cdi-1-7cd9s     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Normal    BackOff                          kubelet, ip-172-31-68-204.us-east-2.compute.internal   Back-off pulling image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:39b9ea0bf18b480c850e46970981ff29b682d156f8475626a4697629b1b8034e"
18m        23m         78        wildfly-camel-example-camel-cdi-1-7cd9s     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-68-204.us-east-2.compute.internal   Error: ImagePullBackOff
23m        23m         1         wildfly-camel-example-camel-cdi-1-deploy    Pod                                                                        Normal    Scheduled                        default-scheduler                                      Successfully assigned wildfly-camel-example-camel-cdi-1-deploy to ip-172-31-64-128.us-east-2.compute.internal
23m        23m         1         wildfly-camel-example-camel-cdi-1-deploy    Pod                                                                        Normal    SuccessfulMountVolume            kubelet, ip-172-31-64-128.us-east-2.compute.internal   MountVolume.SetUp succeeded for volume "deployer-token-72qxr" 
23m        23m         1         wildfly-camel-example-camel-cdi-1-deploy    Pod                     spec.containers{deployment}                        Normal    Pulling                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   pulling image "registry.reg-aws.openshift.com:443/openshift3/ose-deployer:v3.9.14"
23m        23m         1         wildfly-camel-example-camel-cdi-1-deploy    Pod                     spec.containers{deployment}                        Normal    Pulled                           kubelet, ip-172-31-64-128.us-east-2.compute.internal   Successfully pulled image "registry.reg-aws.openshift.com:443/openshift3/ose-deployer:v3.9.14"
23m        23m         1         wildfly-camel-example-camel-cdi-1-deploy    Pod                     spec.containers{deployment}                        Normal    Created                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   Created container
23m        23m         1         wildfly-camel-example-camel-cdi-1-deploy    Pod                     spec.containers{deployment}                        Normal    Started                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   Started container
9m         9m          1         wildfly-camel-example-camel-cdi-1-deploy    Pod                     spec.containers{deployment}                        Normal    Killing                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   Killing container with id docker://deployment:Need to kill Pod
23m        23m         1         wildfly-camel-example-camel-cdi-1           ReplicationController                                                      Normal    SuccessfulCreate                 replication-controller                                 Created pod: wildfly-camel-example-camel-cdi-1-7cd9s
9m         9m          1         wildfly-camel-example-camel-cdi-1           ReplicationController                                                      Normal    SuccessfulDelete                 replication-controller                                 Deleted pod: wildfly-camel-example-camel-cdi-1-7cd9s
1h         2h          304       wildfly-camel-example-camel-cdi-11-4q95m    Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Normal    BackOff                          kubelet, ip-172-31-68-204.us-east-2.compute.internal   Back-off pulling image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:32aed022e4b1eb40690ac487372d6728ad65d8790185883c1aef9a23b8fb69d6"
1h         2h          283       wildfly-camel-example-camel-cdi-11-4q95m    Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-68-204.us-east-2.compute.internal   Error: ImagePullBackOff
1h         1h          3         wildfly-camel-example-camel-cdi-11-deploy   Pod                                                                        Normal    DeadlineExceeded                 kubelet, ip-172-31-64-128.us-east-2.compute.internal   Pod was active on the node longer than the specified deadline
1h         1h          1         wildfly-camel-example-camel-cdi-11-deploy   Pod                     spec.containers{deployment}                        Normal    Killing                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   Killing container with id docker://deployment:Need to kill Pod
1h         1h          1         wildfly-camel-example-camel-cdi-11          ReplicationController                                                      Normal    SuccessfulDelete                 replication-controller                                 Deleted pod: wildfly-camel-example-camel-cdi-11-4q95m
9m         9m          1         wildfly-camel-example-camel-cdi-2-deploy    Pod                                                                        Normal    Scheduled                        default-scheduler                                      Successfully assigned wildfly-camel-example-camel-cdi-2-deploy to ip-172-31-68-204.us-east-2.compute.internal
9m         9m          1         wildfly-camel-example-camel-cdi-2-deploy    Pod                                                                        Normal    SuccessfulMountVolume            kubelet, ip-172-31-68-204.us-east-2.compute.internal   MountVolume.SetUp succeeded for volume "deployer-token-72qxr" 
9m         9m          1         wildfly-camel-example-camel-cdi-2-deploy    Pod                     spec.containers{deployment}                        Normal    Pulling                          kubelet, ip-172-31-68-204.us-east-2.compute.internal   pulling image "registry.reg-aws.openshift.com:443/openshift3/ose-deployer:v3.9.14"
9m         9m          1         wildfly-camel-example-camel-cdi-2-deploy    Pod                     spec.containers{deployment}                        Normal    Pulled                           kubelet, ip-172-31-68-204.us-east-2.compute.internal   Successfully pulled image "registry.reg-aws.openshift.com:443/openshift3/ose-deployer:v3.9.14"
9m         9m          1         wildfly-camel-example-camel-cdi-2-deploy    Pod                     spec.containers{deployment}                        Normal    Created                          kubelet, ip-172-31-68-204.us-east-2.compute.internal   Created container
9m         9m          1         wildfly-camel-example-camel-cdi-2-deploy    Pod                     spec.containers{deployment}                        Normal    Started                          kubelet, ip-172-31-68-204.us-east-2.compute.internal   Started container
8m         8m          1         wildfly-camel-example-camel-cdi-2-deploy    Pod                     spec.containers{deployment}                        Normal    Killing                          kubelet, ip-172-31-68-204.us-east-2.compute.internal   Killing container with id docker://deployment:Need to kill Pod
9m         9m          1         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                                                                        Normal    Scheduled                        default-scheduler                                      Successfully assigned wildfly-camel-example-camel-cdi-2-wkgmk to ip-172-31-64-128.us-east-2.compute.internal
9m         9m          1         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                                                                        Normal    SuccessfulMountVolume            kubelet, ip-172-31-64-128.us-east-2.compute.internal   MountVolume.SetUp succeeded for volume "default-token-9dl71" 
9m         9m          2         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Normal    Pulling                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   pulling image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:12ed3def3b0c22d62dd7297fd65a6b7b3fbfc289b4da4f5cf8cbc47b59053dfa"
9m         9m          2         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-64-128.us-east-2.compute.internal   Failed to pull image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:12ed3def3b0c22d62dd7297fd65a6b7b3fbfc289b4da4f5cf8cbc47b59053dfa": rpc error: code = Unknown desc = unauthorized: authentication required
9m         9m          2         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-64-128.us-east-2.compute.internal   Error: ErrImagePull
9m         9m          5         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                                                                        Normal    SandboxChanged                   kubelet, ip-172-31-64-128.us-east-2.compute.internal   Pod sandbox changed, it will be killed and re-created.
8m         9m          6         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Normal    BackOff                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   Back-off pulling image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:12ed3def3b0c22d62dd7297fd65a6b7b3fbfc289b4da4f5cf8cbc47b59053dfa"
8m         9m          6         wildfly-camel-example-camel-cdi-2-wkgmk     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-64-128.us-east-2.compute.internal   Error: ImagePullBackOff
9m         9m          1         wildfly-camel-example-camel-cdi-2           ReplicationController                                                      Normal    SuccessfulCreate                 replication-controller                                 Created pod: wildfly-camel-example-camel-cdi-2-wkgmk
8m         8m          1         wildfly-camel-example-camel-cdi-2           ReplicationController                                                      Normal    SuccessfulDelete                 replication-controller                                 Deleted pod: wildfly-camel-example-camel-cdi-2-wkgmk
8m         8m          1         wildfly-camel-example-camel-cdi-3-deploy    Pod                                                                        Normal    Scheduled                        default-scheduler                                      Successfully assigned wildfly-camel-example-camel-cdi-3-deploy to ip-172-31-70-122.us-east-2.compute.internal
8m         8m          1         wildfly-camel-example-camel-cdi-3-deploy    Pod                                                                        Normal    SuccessfulMountVolume            kubelet, ip-172-31-70-122.us-east-2.compute.internal   MountVolume.SetUp succeeded for volume "deployer-token-72qxr" 
8m         8m          1         wildfly-camel-example-camel-cdi-3-deploy    Pod                     spec.containers{deployment}                        Normal    Pulling                          kubelet, ip-172-31-70-122.us-east-2.compute.internal   pulling image "registry.reg-aws.openshift.com:443/openshift3/ose-deployer:v3.9.14"
8m         8m          1         wildfly-camel-example-camel-cdi-3-deploy    Pod                     spec.containers{deployment}                        Normal    Pulled                           kubelet, ip-172-31-70-122.us-east-2.compute.internal   Successfully pulled image "registry.reg-aws.openshift.com:443/openshift3/ose-deployer:v3.9.14"
8m         8m          1         wildfly-camel-example-camel-cdi-3-deploy    Pod                     spec.containers{deployment}                        Normal    Created                          kubelet, ip-172-31-70-122.us-east-2.compute.internal   Created container
8m         8m          1         wildfly-camel-example-camel-cdi-3-deploy    Pod                     spec.containers{deployment}                        Normal    Started                          kubelet, ip-172-31-70-122.us-east-2.compute.internal   Started container
8m         8m          1         wildfly-camel-example-camel-cdi-3-v6qrd     Pod                                                                        Normal    Scheduled                        default-scheduler                                      Successfully assigned wildfly-camel-example-camel-cdi-3-v6qrd to ip-172-31-64-128.us-east-2.compute.internal
8m         8m          1         wildfly-camel-example-camel-cdi-3-v6qrd     Pod                                                                        Normal    SuccessfulMountVolume            kubelet, ip-172-31-64-128.us-east-2.compute.internal   MountVolume.SetUp succeeded for volume "default-token-9dl71" 
8m         8m          2         wildfly-camel-example-camel-cdi-3-v6qrd     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Normal    Pulling                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   pulling image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:12ed3def3b0c22d62dd7297fd65a6b7b3fbfc289b4da4f5cf8cbc47b59053dfa"
8m         8m          2         wildfly-camel-example-camel-cdi-3-v6qrd     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-64-128.us-east-2.compute.internal   Failed to pull image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:12ed3def3b0c22d62dd7297fd65a6b7b3fbfc289b4da4f5cf8cbc47b59053dfa": rpc error: code = Unknown desc = unauthorized: authentication required
8m         8m          2         wildfly-camel-example-camel-cdi-3-v6qrd     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-64-128.us-east-2.compute.internal   Error: ErrImagePull
8m         8m          7         wildfly-camel-example-camel-cdi-3-v6qrd     Pod                                                                        Normal    SandboxChanged                   kubelet, ip-172-31-64-128.us-east-2.compute.internal   Pod sandbox changed, it will be killed and re-created.
8m         8m          5         wildfly-camel-example-camel-cdi-3-v6qrd     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Normal    BackOff                          kubelet, ip-172-31-64-128.us-east-2.compute.internal   Back-off pulling image "docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi@sha256:12ed3def3b0c22d62dd7297fd65a6b7b3fbfc289b4da4f5cf8cbc47b59053dfa"
3m         8m          46        wildfly-camel-example-camel-cdi-3-v6qrd     Pod                     spec.containers{wildfly-camel-example-camel-cdi}   Warning   Failed                           kubelet, ip-172-31-64-128.us-east-2.compute.internal   Error: ImagePullBackOff
8m         8m          1         wildfly-camel-example-camel-cdi-3           ReplicationController                                                      Normal    SuccessfulCreate                 replication-controller                                 Created pod: wildfly-camel-example-camel-cdi-3-v6qrd
1h         1h          1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    ReplicationControllerScaled      deploymentconfig-controller                            Scaled replication controller "wildfly-camel-example-camel-cdi-11" from 1 to 0
23m        23m         1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    DeploymentCreated                deploymentconfig-controller                            Created new replication controller "wildfly-camel-example-camel-cdi-1" for version 1
9m         9m          1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    DeploymentCancelled              deploymentconfig-controller                            Cancelled deployment "wildfly-camel-example-camel-cdi-1" superceded by version 2
9m         9m          8         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    DeploymentAwaitingCancellation   deploymentconfig-controller                            Deployment of version 2 awaiting cancellation of older running deployments
9m         9m          1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    RolloutCancelled                 deployer-controller                                    Rollout for "ppalaga-stage/wildfly-camel-example-camel-cdi-1" cancelled
9m         9m          1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    DeploymentCreated                deploymentconfig-controller                            Created new replication controller "wildfly-camel-example-camel-cdi-2" for version 2
8m         8m          1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    DeploymentCancelled              deploymentconfig-controller                            Cancelled deployment "wildfly-camel-example-camel-cdi-2" superceded by version 3
8m         8m          11        wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    DeploymentAwaitingCancellation   deploymentconfig-controller                            Deployment of version 3 awaiting cancellation of older running deployments
8m         8m          1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    RolloutCancelled                 deployer-controller                                    Rollout for "ppalaga-stage/wildfly-camel-example-camel-cdi-2" cancelled
8m         8m          1         wildfly-camel-example-camel-cdi             DeploymentConfig                                                           Normal    DeploymentCreated                deploymentconfig-controller                            Created new replication controller "wildfly-camel-example-camel-cdi-3" for version 3
@ppalaga
Copy link
Contributor Author

ppalaga commented Apr 10, 2018

The image is really there in the registry. When I create the app manually in ppalaga-jenkins namespace the deployment succeeds:

oc project ppalaga-jenkins
oc get is
NAME                              DOCKER REPO                                                                        TAGS      UPDATED
wildfly-camel-example-camel-cdi   docker-registry.default.svc:5000/ppalaga-jenkins/wildfly-camel-example-camel-cdi   latest    2 hours ago
oc new-app ppalaga-jenkins/wildfly-camel-example-camel-cdi
oc expose dc wildfly-camel-example-camel-cdi

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/

@ppalaga
Copy link
Contributor Author

ppalaga commented Apr 10, 2018

It works when I do the same steps with the spring-boot quickstart. I wonder where is the difference.

@sunilk747
Copy link
Collaborator

sunilk747 commented Jun 12, 2018

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:
screenshot from 2018-06-12 17-54-11
cc: @pradeepto @krishnapaparaju @piyush1594

@animuk
Copy link
Collaborator

animuk commented Jun 13, 2018

@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.
Please note: this issue is only affecting the user's repo. For Boosters, things are working fine.

@ppalaga
Copy link
Contributor Author

ppalaga commented Jun 13, 2018

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

@stranvi
Copy link

stranvi commented Jul 12, 2018

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):
$ oc delete po,dc,rc,svc,route -l app=myapp

The Image I was trying to pull was just some custom specific Java/SpringBoot application.

@giacomolm
Copy link

Is this causing issues like the one below ?

Failed to pull image "registry.reg-aws.openshift.com:443/openshift3/ose-deployer:v3.11.0-0.21.0": rpc error: code = Unknown desc = unable to retrieve auth token: invalid username/password

@stranvi
Copy link

stranvi commented Sep 25, 2018

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):
$ oc delete po,dc,rc,svc,route -l app=myapp

The Image I was trying to pull was just some custom specific Java/SpringBoot application.

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.

@Oliboy50
Copy link

@giacomolm I have your issue very very frequently on starter-us-east-1 this week

Have you told openshit maintainers about this?

@theangrydev
Copy link

I am also having this issue with a fresh starter-us-east-1 with the first attempt at Jenkins install via the catalog

@giacomolm
Copy link

Hi @Oliboy50 @theangrydev
I've contacted the free support and they told me they are aware of this issue. In my case was solved after couple of hours, but I had the same trouble two days after: probably they are working on it and the fix is not stable. I will try again to play around tomorrow and I will let you know in case I've the same issue

@hrishin
Copy link

hrishin commented Nov 5, 2018

This is more of OpenShift issue. Removing tag from build team.

@hodrigohamalho
Copy link

Just face this same issue.
Step by step that I did:
Create a private image in quay.io
Deploy image in Openshift
Run two or three times and this start to happen.
For now, my workaround is build application from scratch on Openshift every time.

@Katka92
Copy link

Katka92 commented May 13, 2019

I can see this problem in our periodic jobs today too. Job runs with user provisioned on starter-us-east-1b.

@rikirenz
Copy link

+1

@djbrown
Copy link

djbrown commented Jul 19, 2019

In my case it was an error in my buildconfig. I had to fix / remove an invalid image pull secret reference in the yaml.

@hodrigohamalho
Copy link

I just inserted the imagePullPolicy: IfNotPresent attribute in the deployment config:

@lkravi
Copy link

lkravi commented Aug 26, 2019

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests