NetworkManager on node fails resulting into node getting NotReady

Solution Verified - Updated -

Issue

  • The node turns to NotReady intermittently losing connectivity to RHOCP cluster with no SSH access.

  • The node console log shows NetworkManager getting stopped by systemd.

        systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated
    NetworkManager[xxx]: <info>  [xxxx.xxxx] caught SIGTERM, shutting down normally.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.16, 4.18

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