If we're expecting network devices to come up, we need to tell dracut to wait for devices to activate before proceeding to stage 2, otherwise we won't have ifcfg files, and the NM handover will fail, and anaconda considers it a fatal error if a network device isn't active when the kickstart says it should be. (It would be nice if anaconda could set up the network itself so we didn't have to handle this all in initramfs..) --- dracut/parse-anaconda-net.sh | 8 +++++++- 1 files changed, 7 insertions(+), 1 deletions(-) diff --git a/dracut/parse-anaconda-net.sh b/dracut/parse-anaconda-net.sh index 4a69280..39fbf37 100755 --- a/dracut/parse-anaconda-net.sh +++ b/dracut/parse-anaconda-net.sh @@ -62,9 +62,15 @@ elif [ -n "$ip" ]; then # just good ol' ipv4 fi [ -n "$ip$ipv6$ksdev_val" ] && set_neednet +unset CMDLINE + +# if network is needed, make sure the "online" hook runs +if getarg rd.neednet >/dev/null; then + initqueue --finished --unique --name "online" \ + [ -e /tmp/net.ifaces ] '&&' all_ifaces_up +fi # set dhcp vendor class dhcpclass=$(getarg inst.dhcpclass) || dhcpclass="anaconda-$(uname -srm)" echo "send vendor-class-identifier \"$dhcpclass\"" >> /etc/dhclient.conf -unset CMDLINE -- 1.7.7.6 _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
