Bug 1908908
Summary: | [sig-builds][Feature:Builds] Optimized image builds should succeed | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | jamo luhrsen <jluhrsen> |
Component: | Build | Assignee: | Adam Kaplan <adam.kaplan> |
Status: | CLOSED DUPLICATE | QA Contact: | XiuJuan Wang <xiuwang> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.6 | CC: | aos-bugs, gmontero |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
[sig-builds][Feature:Builds] Optimized image builds should succeed
|
|
Last Closed: | 2020-12-22 14:09:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
jamo luhrsen
2020-12-17 21:33:24 UTC
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 *** |