How to make bonds always use the first slave interface's MAC address in Red Hat OpenShift Container Platform 4

Solution In Progress - Updated -

Issue

How to make bonds always use the first slave interface's MAC address in Red Hat OpenShift Container Platform 4.

Starting with Red Hat OpenShift Container Platform 4.10, on node reboot, the ovs-configuration.service running the configure-ovs.sh script tears down br-ex and reconfigures the main bond interface that was attached to br-ex. At that point in time, the bond's second slave member might be enslaved first and the recreated bond interface will use the secondary's MAC address. Subsequent attempts to obtain a DHCP lease - and thus a default route - might fail.

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