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

Bug 1772188

Summary:	GCP 4.3 cluster frequently fail to pull from internal image registry with "no route to host"
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Networking	Assignee:	Casey Callendrello <cdc>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	urgent
Priority:	unspecified
Version:	4.3.0
Target Milestone:	---
Target Release:	---
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:	2019-11-14 12:51:28 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 Clayton Coleman 2019-11-13 20:50:55 UTC

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-compact-4.3/18

[Feature:Builds] result image should have proper labels set S2I build from a template should create a image from "test-s2i-build.json" template with proper Docker labels [Suite:openshift/conformance/parallel] expand_less	1m22s
fail [github.com/openshift/origin/test/extended/builds/labels.go:50]: Expected
    <bool>: false
to be true

...

Host code (cri-o) fails to reach image-registry over service network with no route to host:

[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.imagestore=/var/lib/shared]image-registry.openshift-image-registry.svc:5000/e2e-test-build-sti-labels-mp8wv/test:latest" to "docker://image-registry.openshift-image-registry.svc:5000/e2e-test-build-sti-labels-mp8wv/test:latest": Error trying to reuse blob sha256:57c14dd66db0390dbf6da578421c077f6de8e88edd0815b4caa94607ba5f4c09 at destination: error pinging docker registry image-registry.openshift-image-registry.svc:5000: Get https://image-registry.openshift-image-registry.svc:5000/v2/: dial tcp 172.30.130.240:5000: connect: no route to host

Happens relatively frequently over time (every minute or so in a chunk we had tests fail). Is happening in a lot of GCP runs - 1/10-1/7.  Setting priority high until we can reduce the importance.

This is familiar to many previous no route to host issues on GCP.

Comment 1 Casey Callendrello 2019-11-14 12:51:28 UTC


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