You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2021. It is now read-only.
Management of /etc/modprobe.d/bonding.conf file is not currently done by the network::interface define, you can easily build a wrapper around it, which declares the relevant network::interface define and whatever else you need
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Testing your module with hiera on CentOS 7 (I saw you had not tested this version yet).
puppetserver-2.2.1-1.el7.noarch
Linux 3.10.0-327.4.4.el7.x86_64
network::interfaces_hash:
eth0:
method: manual
allow_hotplug: 'eth0'
master: 'bond0'
slave: 'yes'
eth1:
method: manual
allow_hotplug: 'ens6'
master: 'bond0'
slave: 'yes'
bond0:
ipaddr: '192.168.1.4'
netmask: '255.255.255.0'
gateway: '192.168.177.1'
dns1: '192.168.177.2'
dns2: '192.168.177.3'
bond_mode: 'balance-rr'
bond_miimon: '100'
systemctl status networking.service -l shows:
"...Device bond0 does not seem to be present, delaying initialization"
Adding to /etc/modprobe.d/bonding.conf
alias bond0 bonding
After doing this, the network starts without issue. I would like to use this to manage multiple bonded interfaces.
The text was updated successfully, but these errors were encountered: