Bug 1665763

Summary:	After upgrading 3.9 to 3.10 applications are getting intermittent 'No route to host' exceptions.
Product:	OpenShift Container Platform	Reporter:	emahoney
Component:	Networking	Assignee:	Casey Callendrello <cdc>
Status:	CLOSED DUPLICATE	QA Contact:	Meng Bo <bmeng>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.10.0	CC:	aos-bugs, bbennett, cdc, dageoffr, emahoney, rhowe, stwalter
Target Milestone:	---
Target Release:	3.10.z
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-03-26 16:08:01 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 emahoney 2019-01-13 20:56:56 UTC

Description of problem: After upgrading 3.9 to 3.10 applications are getting 'No route to host' exceptions. Deleting the SDN pod on the node seems to resolve the issue temporarily. 

We also see that curling the endpoint IP from the router shows 'No Route to host'. This env is using ovs-networkpolicy plugin.


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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: Applications intermittently get 'No route to host' exceptions


Expected results: Application able to resolve a .svc and access that endpoint. 


Additional info:

Comment 17 Ryan Howe 2019-01-23 16:14:41 UTC

At the time of any issue where a pod gets "getsockopt: no route to host" when connecting to the Kubernetes service IP.

The output of iptables nat table is needed. 

The likely reasons for this issue are either the NAT rules are not updated on the nodes or the masters api endpoints are not healthy.

Comment 18 Ben Bennett 2019-03-26 16:08:01 UTC


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