livenet/network does not respect bootdev when using bonds

[bcg62]

In a situation where I am live booting a rootfs.img tarball, on its own this works perfectly.

Upon expanding my configuration to include a bond, it seems the bond is built and ifup'd before bootdev is. This causes livenet to trigger fetch-liveupdate.sh on a network connection that will not have access to the provided live image.

Example configuration

bootdev=enp0s3 bond=bond0:p3p1,p2p1:mode=4 ip=enp0s3:dhcp ip=192.168.0.5::192.168.0.1:255.255.0.0::bond0::none

I suspect the better approach is to ensure the network module ifup's bootdev first if it exists. Otherwise livenet needs to ingore taking action unless bootdev is what triggered the initqueue.

[bcg62]

I believe this is also addressed here.

e6ae0c6

[stale]

This issue is being marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. If this is still an issue in the latest release of Dracut and you would like to keep it open please comment on this issue within the next 7 days. Thank you for your contributions.