Is it possible to configure bonding during installation of Red Hat CoreOS 4.2 on bare metal (UPI Installation)?
Issue
- How can one configure Network Bonding across multiple NICs in BareMetal OCP (Red Hat CoreOS) 4.2 installation?
- Booting Red Hat CoreOS 4.2 with command line parameters for bonding fail with the following errors and lands into
dracut
shell.
[ 20.537685] localhost systemd[1]: Started Ignition (files).
[ 20.544208] localhost systemd[1]: Starting Reload Configuration from the Real Root...
[ 20.551223] localhost systemd[1]: Started Tear down initramfs networking.
[ 20.560631] localhost systemd[1]: Reloading.
[ 20.702108] localhost systemd[1]: Started Reload Configuration from the Real Root.
[ 20.711488] localhost systemd[1]: Reached target Initrd File Systems.
[ 20.719451] localhost systemd[1]: Reached target Initrd Default Target.
[ 20.727834] localhost systemd[1]: Starting dracut pre-pivot and cleanup hook...
[ 20.746834] localhost dracut-pre-pivot[1362]: cat: /sys/class/net/bond0/name_assign_type: Invalid argument
[ 20.882653] localhost dracut-pre-pivot[1362]: Dec 06 13:12:28 | /etc/multipath.conf does not exist, blacklisting all devices.
[ 20.882653] localhost dracut-pre-pivot[1362]: Dec 06 13:12:28 | You can run "/sbin/mpathconf --enable" to create
[ 20.882653] localhost dracut-pre-pivot[1362]: Dec 06 13:12:28 | /etc/multipath.conf. See man mpathconf(8) for more details
[ 20.932259] localhost systemd[1]: Started dracut pre-pivot and cleanup hook.
[ 20.932606] localhost systemd[1]: Starting Cleaning Up and Shutting Down Daemons...
[ 20.932653] localhost systemd[1]: Stopping Tear down initramfs networking...
[ 20.932670] localhost coreos-teardown-initramfs-network[1424]: Cannot find device "bonding_masters"
[ 20.939091] localhost systemd[1]: Stopped target Timers.
Environment
- Red Hat OpenShift Container Platform
- Red Hat CoreOS 4.2 onwards
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.