Description of problem: When a bonded interface is brought up, any slaves included in the bond have their hardware address set to that of the bond master. Although this allows an interface to be brought up on start up, when the configuration file is imported into the booted system it prevents the bonded interface being successfully restarted. The fix involves obtaining the hardware address of the slaves before they are added to the bond and then using this value in the configuration file. Version-Release number of selected component (if applicable): Fedora 20 x86_64; Dracut 037-11.git20140402 How reproducible: Steps to Reproduce: 1. Setup bonded interface in /boot/grub2/grub.cfg (parameters below) 2. Reboot 3. Actual results: The bonded interface is brought up correctly during the initial boot process but when the system is fully operational the bonded interface is down. The configuration files (ifcfg-enp1s0f0, ifcfg-enp1s0f1) imported into the booted system both use the hardware address from the bond master, meaning a restart of the bonded interface fails. Expected results: The bonded interface works both during the initial boot process (initramfs image produced by dracut) and once the system is fully operational. Additional info: Relevant grub kernel parameters: bond=bond0:enp1s0f0,enp1s0f1 ip=bond0:dhcp Suggested Patch (Original commit and pull request on GitHub): https://github.com/cyclops8456/dracut/commit/f7a87b486547ca5792be2f1ee78eacb9672140a9 https://github.com/haraldh/dracut/pull/19
Created attachment 894865 [details] Copy of proposed patch / pull request on GitHub
Are there any test cases etc I need to run this against to make sure it's fine? I've tested in a few systems (all Fedora 20) that I have access to and it works as expected on those; fixing the issue I was having when bringing a bonded interface up during the initial boot process.
http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=83c9ff7dbb465bedb10119bb2883d34266922180
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.