Idled services cannot wake up automatically after restart of ovnkube-master in Red Hat OpenShift Container Platform 4

Solution Verified - Updated -

Issue

Idled services cannot be woken up automatically after the leader ovnkube-master process is restarted or after the ovnkube-master leader changes.

For example, this affects services which are idled during a cluster upgrade. When such a service receives network traffic, it is not woken up automatically.

Environment

Red Hat OpenShift Container Platform 4.6
Red Hat OpenShift Container Platform 4.7

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