Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu 20.04 bonded interfaces don't work -- explicitly disables slave/member interfaces in manifests/bond/debian.pp #288

Open
legooolas opened this issue Nov 10, 2022 · 0 comments · May be fixed by #289

Comments

@legooolas
Copy link

legooolas commented Nov 10, 2022

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: All (tested on 6.28.0)
  • Ruby: 2.5.9p229 from Puppet 6
  • Distribution: Testing on Ubuntu 20.04 (but affects any Debian-based distro?)
  • Module version: github head, or 1.0.1 from Puppet Forge give same behaviour

How to reproduce (e.g Puppet code you use)

network::bond { 'bond0':
  ensure    => 'present',
  hotplug   => false,
  family    => 'inet'
  method    => 'none',
  ipaddress => '1.2.3.4',
  netmask   => '255.255.255.0',
  onboot    => true,
  slaves    => ['eth0', 'eth1'],
  mode      => 'active-backup',
  miimon    => '100',
}

What are you seeing

Slave interfaces are explicitly disabled in manifests/bond/debian.pp but they need basic configuration in the interfaces file to be present for them to become a member of the bond.

What behaviour did you expect instead

Calling network_config to add slave interfaces as bond members.

Output log

Can provide more logging info, but Puppet ensures that the slave interface configs are absent, as requested in the network::bond::debian class by network_config { $slaves: ... }

Any additional information you'd like to impart

The network::bond::redhat class does the right thing here and sets ensure to the same as the bond interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant