[OVN] no route to host for POD to POD communication

Solution Verified - Updated -

Issue

  • "no route to host" event detected for POD to POD communication, affecting cluster operators and potentially applications as well

  • During the upgrade process from 4.7.37 to 4.7.40, at least one pod is completely unable to reach the cluster IP of kubernetes.default.svc.cluster.local. The error is like this:

    2022-01-20T11:08:48.475043081Z F0120 11:08:48.474981       1 cmd.go:72] unable to load configmap based request-header-client-ca-file: Get "https://172.30.0.1:443/api/v1/namespaces/kube-system/configmaps/extension- 
apiserver-authentication?timeout=10s": dial tcp 172.30.0.1:443: connect: no route to host

Environment

  • Openshift Container Platform (RHOCP)

    • 4.7.40+

  • OVN-Kubernetes as virtualized network for pod and service networks

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content