Bug 1908908 - [sig-builds][Feature:Builds] Optimized image builds should succeed
Summary: [sig-builds][Feature:Builds] Optimized image builds should succeed
Keywords:
Status: CLOSED DUPLICATE of bug 1905095
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Adam Kaplan
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-17 21:33 UTC by jamo luhrsen
Modified: 2020-12-22 14:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
[sig-builds][Feature:Builds] Optimized image builds should succeed
Last Closed: 2020-12-22 14:09:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Gabe Montero 2020-12-18 19:53:25 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

Comment 2 Adam Kaplan 2020-12-22 14:09:43 UTC

*** This bug has been marked as a duplicate of bug 1905095 ***


Note You need to log in before you can comment on or make changes to this bug.