Created attachment 1558987 [details] error occurrences Description of problem: openshift-tests [Feature:Builds][Conformance] oc new-app should succeed with a --name of 58 characters [Suite:openshift/conformance/parallel/minimal] is failing with a rate of 30% STEP: waiting for the build to complete Apr 26 04:09:18.972: INFO: WaitForABuild returning with error: The build "a234567890123456789012345678901234567890123456789012345678-1" status is "Failed" Apr 26 04:09:18.980: INFO: Running 'oc logs --config=/tmp/admin.kubeconfig --namespace=e2e-test-new-app-n4sxr -f bc/a234567890123456789012345678901234567890123456789012345678 --timestamps' Apr 26 04:09:19.363: INFO: build logs : 2019-04-26T04:08:54.572152656Z Cloning "https://github.com/sclorg/nodejs-ex" ... 2019-04-26T04:08:55.462236653Z Commit: e59fe7571f883db2ae2e53d555aef6d145c6f032 (Merge pull request #206 from liangxia/okd) 2019-04-26T04:08:55.462236653Z Author: Honza Horak <hhorak> 2019-04-26T04:08:55.462236653Z Date: Tue Oct 16 15:45:10 2018 +0200 2019-04-26T04:08:57.649954307Z Caching blobs under "/var/cache/blobs". 2019-04-26T04:08:58.161781965Z Warning: Pull failed, retrying in 5s ... 2019-04-26T04:09:03.623578368Z Warning: Pull failed, retrying in 5s ... 2019-04-26T04:09:09.156032661Z Warning: Pull failed, retrying in 5s ... 2019-04-26T04:09:14.349781882Z error: build error: After retrying 2 times, Pull image still failed due to error: while pulling "docker://registry.redhat.io/rhoar-nodejs/nodejs-10@sha256:cd0003f4abfa61f4e801ca498acb20120008ecd3ea7ce7bb618e06ab7b2f8b1d" as "registry.redhat.io/rhoar-nodejs/nodejs-10@sha256:cd0003f4abfa61f4e801ca498acb20120008ecd3ea7ce7bb618e06ab7b2f8b1d": Error determining manifest MIME type for docker://registry.redhat.io/rhoar-nodejs/nodejs-10@sha256:cd0003f4abfa61f4e801ca498acb20120008ecd3ea7ce7bb618e06ab7b2f8b1d: unable to retrieve auth token: invalid username/password Version-Release number of selected component (if applicable): 4.1 How reproducible: CI e2e-aws builds Additional info:
*** This bug has been marked as a duplicate of bug 1702743 ***