On 6/23/23 08:32, Duraisankar P via discuss wrote: > Hello, > > We have an issue while adding an interface to OVS bond during bootup. > > Issue : > Whenever a default interface name is used eg: eth0 , eth1 in the OVS bond, > there might be a chance for the interface name to be changed from eth0=>eth1 > or vice versa during the bootup. In this case, OVS bonding does not detect > the udev changes and only monitors the RTNETLINK events. Due to this, wrong > interfaces might be added to the OVS bond or it would be an improper > configuration. > > Is there any alternative to solve this issue caused by the udev changes ? The > possible alternative which we could think of is to add udev rules or add a > custom interface name to the OVS bond instead of standard interface names > untill the udev interface names settle.
You should be able to fix udev issue with more udev. For quite a few years now it should support predictable device names based on BIOS config or PCI location of your actual NIC: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Best regards, Ilya Maximets. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
