After enabling IPSec in OpenShift, nodes go NotReady with i/o timeout
Issue
- Enabled IPSec. All nodes work except 2 nodes do not. These 2 get i/o timeout reaching to master
Sep 10 11:47:51 node1.example.com atomic-openshift-node[15759]: F0910 11:47:51.294354 15759 start_node.go:140] cannot fetch "default" cluster network: Get https://test.example.com/url?k=e2df2707d628217a.e2dfc2cf-fe2bc6c48149e7e4&u=https://master1.example.com:8443/oapi/v1/clusternetworks/default: dial tcp 10.230.60.39:8443: i/o timeout
- Cannot start atomic-openshift-node after network changes
- We did upgrade and all worked fine. The we started ipsec and the server became NOTREADY. Tried restating atomic-openshift-node and it does not come up.
- br0 mtu is not set properly after making changes to the node-config.yaml
Environment
- Red Hat OpenShift Container Platform
- 3.6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
