test: [sig-builds][Feature:Builds] Optimized image builds should succeed is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-builds%5C%5D%5C%5BFeature%3ABuilds%5C%5D+Optimized+image+builds++should+succeed -and- test: [sig-builds][Feature:Builds] Multi-stage image builds should succeed is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-builds%5C%5D%5C%5BFeature%3ABuilds%5C%5D+Multi-stage+image+builds++should+succeed both tests are found as top failing cases for 4.6, and no bug assigned: https://sippy.ci.openshift.org/?release=4.6#TopFailingTestsWithoutABug example job: https://prow.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-mirrors-4.6
Per the analysis in https://coreos.slack.com/archives/C014MHHKUSF/p1608314861313400 this looks like a manifestation of https://bugzilla.redhat.com/show_bug.cgi?id=1905095 Seeing this type of error trying to access images from the internal image registry that correspond to imagestreamtags the build tests use: error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: while pulling "docker://image-registry.openshift-image-registry.svc:5000/openshift/tools:latest" as "image-registry.openshift-image-registry.svc:5000/openshift/tools:latest": Error initializing source docker://image-registry.openshift-image-registry.svc:5000/openshift/tools:latest: Error reading manifest latest in image-registry.openshift-image-registry.svc:5000/openshift/tools: unknown: unable to pull manifest from registry.svc.ci.openshift.org/ci-op-h24h13l7/release-scratch@sha256:091cd1158444af8382312b71150d26e6550c5d52023b993fec6afd2253d2e425: manifest unknown: manifest unknown
*** This bug has been marked as a duplicate of bug 1905095 ***