View Issue Details

IDProjectCategoryView StatusLast Update
0016497CentOS-7anacondapublic2019-09-30 15:46
ReporterTom Mercelis 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version7.6.1810 
Target VersionFixed in Version 
Summary0016497: Network with bonding configured from kickstart does not work with network service (NetworkManager disabled)
DescriptionDuring a kickstart setup with bonding configured the bond0 is up and downloading packages, after the first boot however, bond0 has no slaves.
NetworkManager is disabled by kickstart.
Steps To ReproduceIn the kickstart:

network --noipv4 --noipv6 --activate --onboot=on --device=bond0 --bondslaves=eno49,eno50 --bondopts=downdelay=0,miimon=1,mode=active-backup,primary=eno49,updelay=0 --mtu 9000
network --bootproto=static --noipv6 --activate --onboot=on --device=bond0 --vlanid=1234 --ip=10.18.0.10 --netmask=255.255.255.0 --gateway=10.18.0.1 --nameserver=8.8.8.8 --mtu=9000
services --disabled=firewalld,NetworkManager

Additional InformationAfter this install, the files ifcfg-bond0_slave_1 and _2 look like:
# Generated by parse-kickstart
NAME="bond0_slave_1"
MASTER="feaa55ce-af0a-4d20-b74f-3ba7a1990bee"
DEVICE="eno49"
TYPE="Ethernet"
ONBOOT="yes"
UUID="31429a87-b9a3-4e5e-95ce-7da3eaab7944"

And /proc/net/bonding/bond0 shows no slave devices.
After replacing UUID of the master device with the device name, and adding a line SLAVE=yes (and a systemctl restart network); the bond does come up with both slave interfaces
...
MASTER="bond0"
SLAVE=yes
...

I've checked this bug as well: https://bugzilla.redhat.com/show_bug.cgi?id=1583709 but in my tests there are no ifcfg-eno(49|50) files created.
Currently I work around this by adding to kickstart %post the two corrections I suggested above.
TagsNo tags attached.
abrt_hash
URL

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-09-30 15:46 Tom Mercelis New Issue