TLS handshake error in OpenShift master API logs

Solution Verified - Updated -

Issue

  • TLS handshake error in OpenShift master API logs every 5-30 sec:

    atomic-openshift-master-api: Ixxxx logs.go:41] http: TLS handshake error from xx.xx.xx.xx:xxxxx: EOF
    
  • During deployment the master does not start. At the master API logs throws:
master.example.com systemd[1]: Unit ovirt-guest-agent.service entered failed state.
master.example.com systemd[1]: ovirt-guest-agent.service failed.
master.example.com atomic-openshift-master-api[2107]: I1114 13:55:03.524776    2107 logs.go:41] http: TLS handshake error from 100.10.200.3:2684: EOF
master.example.com atomic-openshift-master-api[2107]: I1114 13:55:33.526019    2107 logs.go:41] http: TLS handshake error from 100.10.200.3:2714: EOF
master.example.com atomic-openshift-master-api[2107]: I1114 13:56:03.529583    2107 logs.go:41] http: TLS handshake error from 100.10.200.3:2742: EOF
master.example.com atomic-openshift-master-api[2107]: I1114 13:56:33.530198    2107 logs.go:41] http: TLS handshake error from 100.10.200.3:2772: EOF
master.example.com atomic-openshift-master-api[2107]: E1114 13:56:46.355473    2107 repair.go:160] the cluster IP 172.30.0.0 for service kubernetes/default is not within the service CIDR 172.35.0.0/16; please recreate
master.example.com atomic-openshift-master-api[2107]: I1114 13:57:03.530166    2107 logs.go:41] http: TLS handshake error from 100.10.200.3:2800: EOF

Environment

  • Red Hat OpenShift Container Platform 3.9

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