Why sriov-config-daemon triggers node drain after SNNP has finished configuration

Solution Unverified - Updated -

Issue

  • SNNP (SriovNetworkNodePolicy) has finished initial configuration. The user didn't touch the SNNP but the node is drained unexpectedly

Environment

  • Red Hat OpenShift Container Platform 4

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