Nodes with teamd lost connectivity midway through playbook run

Solution Verified - Updated -

Issue

  • App nodes stopped responding to any network connections after the "restart dnsmasq" line in the playbook.
  • A restart of dnsmasq or NetworkManager causes broken pipe and unreachable messages
RUNNING HANDLER [openshift_node_dnsmasq : restart dnsmasq] **********************************************************************************************************************************
changed: [test1.example.net]
changed: [test2.example.net]
changed: [test3.example.net]

fatal: [changed: [test1.example.net]: UNREACHABLE! => {
    "changed": false,
    "unreachable": true
}

MSG:

Failed to connect to the host via ssh: mux_client_request_session: read from master failed: Broken pipe
ssh: connect to host test1.example.net port 22: Connection timed out
  • When using teamd interfaces, my OpenShift nodes have network problems randomly

Environment

  • Red Hat OpenShift Container Platform
    • 3.x
  • Teamd before 1.27-4
    • libteam-1.27-4.el7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.