Red Hat Bugzilla – Bug 1420708
Stable bond slaves ordering based on the device name
Last modified: 2018-02-01 01:40:25 EST
Description of problem:
The order in which slaves are attached to a bond is currently unstable, causing some inconsistent behaviour that affects the bond mac address.
In order to try and be consistent and in sync with initscripts logic, it is suggested here to order the slaves attachment by the device name alphabetically.
The alternative of fixing the mac address is not always suitable, especially when the control of devices may be transferred from NM to other controllers (like in the current RHV agent case) and the complexity introduced to the NM user, which needs in such a case to manage these mac addresses.
This is a major issue on bond usage in Cockpit in the RHV hypervisor.
Can we propose this to z stream?
Pushed upstream branch bg/slaves-order-rh1420708 for review.
The branch LGTM
*** Bug 1387506 has been marked as a duplicate of this bug. ***
(In reply to Beniamino Galvani from comment #4)
> Pushed upstream branch bg/slaves-order-rh1420708 for review.
As stated here , initscripts simply ignore interfaces that appear
too late in the boot process and thus any late slave device will not
even be activated. NM works better in this situation because it
activates the slave when it appears, but of course it can't guarantee
the order of activation. For such corner cases, the suggested solution
is to set a fixed MAC address on the bond.
To wrap this up, I would merge bg/slaves-order-rh1420708 so that at
least we have an activation order consistent with initscripts in most
of the cases.
Merged to master:
Can you please clone this one?
(In reply to Yaniv Dary from comment #18)
> Can you please clone this one?
Do you want this to be cloned for 7.3.z? As stated in comment 5 and comment 8, we don't think this change is suitable for z-stream inclusion.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.