Bug 2021433

Summary: "[sig-builds][Feature:Builds][pullsearch] docker build where the registry is not specified" test fail permanently on disconnected
Product: OpenShift Container Platform Reporter: Arda Guclu <aguclu>
Component: BuildAssignee: Adam Kaplan <adam.kaplan>
Status: CLOSED ERRATA QA Contact: Jitendar Singh <jitsingh>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.10CC: aos-bugs, pbhattac, spandura
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:26:15 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:

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):
4.10

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

Steps to Reproduce:
https://testgrid.k8s.io/redhat-openshift-ocp-release-4.10-blocking#periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-ovn-ipv6

Actual results:
Test is failing

Expected results:
Test passes or skipped on disconnected

Additional info:

According to the logs;
https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-ovn-ipv6/1457792981883949056

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 104.126.6.159:443: 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.

https://access.redhat.com/errata/RHSA-2022:0056