Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1789583

Summary: [4.1.z] Push to internal registry fails with "no such route to host" error
Product: OpenShift Container Platform Reporter: Adam Kaplan <adam.kaplan>
Component: NetworkingAssignee: Alexander Constantinescu <aconstan>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: aconstan, bbennett
Version: 4.1.z   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: buildcop
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-22 14:49: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:
Embargoed:

Description Adam Kaplan 2020-01-09 20:22:24 UTC 
Description of problem:

Image push to the internal registry fails with "connect: no such route to host" errors. Registry logs indicate that its pod was healthy during the course of the test.


Version-Release number of selected component (if applicable): 4.1.z-nightly


Additional info:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-4.1/1319