Bug 2021433 - "[sig-builds][Feature:Builds][pullsearch] docker build where the registry is not specified" test fail permanently on disconnected
Summary: "[sig-builds][Feature:Builds][pullsearch] docker build where the registry is ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Adam Kaplan
QA Contact: Jitendar Singh
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-09 08:28 UTC by Arda Guclu
Modified: 2022-03-10 16:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:26:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26581 0 None open Bug 2021433: Disable new build test on disconnected 2021-11-09 08:29:28 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:26:37 UTC

Description Arda Guclu 2021-11-09 08:28:41 UTC
Description of problem:
"sig-builds][Feature:Builds][pullsearch] docker build where the registry is not specified Building from a Dockerfile whose FROM image ref does not specify the image registry should create a docker build that has buildah search from our predefined list of image registries and succeed" test is failing permanently
on disconnected metal IPv6 jobs(e2e-metal-ipi-ovn-ipv6) and this blocks new releases.

Version-Release number of selected component (if applicable):

How reproducible:
Run e2e-metal-ipi-ovn-ipv6 on 4.10

Steps to Reproduce:

Actual results:
Test is failing

Expected results:
Test passes or skipped on disconnected

Additional info:

According to the logs;

time="2021-11-08T21:28:44Z" level=warning msg="failed, retrying in 4s ... (3/3). Error: initializing source docker://registry.redhat.io/ubi8/ubi:latest: pinging container registry registry.redhat.io: Get \"https://registry.redhat.io/v2/\": dial tcp connect: network is unreachable"

Comment 5 errata-xmlrpc 2022-03-10 16:26:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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