Bug 1789583 - [4.1.z] Push to internal registry fails with "no such route to host" error
Summary: [4.1.z] Push to internal registry fails with "no such route to host" error
Keywords:
Status: CLOSED DUPLICATE of bug 1790704
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.4.0
Assignee: Alexander Constantinescu
QA Contact: zhaozhanqi
URL:
Whiteboard: buildcop
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-09 20:22 UTC by Adam Kaplan
Modified: 2020-01-22 14:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-22 14:49:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.