Tested using imagestream 4.6-art-latest-2021-04-27-142853. A worker with a bonded primary interface deployed and became available without intervention. [root@ocp2-worker-4 ~]# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: ens192 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 Slave Interface: ens192 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:50:56:b7:ff:45 Slave queue ID: 0 Slave Interface: ens224 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:50:56:b7:9f:70 Slave queue ID: 0 [root@ocp2-worker-4 ~]# nmcli con NAME UUID TYPE DEVICE ovs-if-br-ex ec7e3cde-40c7-4e82-90d8-c3530185f0d7 ovs-interface br-ex br-ex f984dd2d-ed10-4110-b588-c82ae5af7120 ovs-bridge br-ex ens192 1183a398-1af0-437b-819f-9fc8daa07477 ethernet ens192 ens224 d528c7c9-ad33-4dda-b94f-da1d911ee017 ethernet ens224 ovs-if-phys0 440dda22-8863-4a0c-bb79-3aae0d2a061c bond bond0 ovs-port-br-ex bbe3c012-8792-46ac-9b4f-718b9d51b713 ovs-port br-ex ovs-port-phys0 3026ca92-2892-4e2a-a879-6cd4a88ca96f ovs-port bond0 bond0 5756428d-990e-451d-a00f-8efa04cae30e bond --
Thanks Andrew. Moving this to verified based on comment 3.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6.27 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1427