Bug #10805
closed
VLAN interface attached to bond is wrongly created as Bond
Description
Hi, I've been using Foreman successfully since 1.2, to manage an
engineering lab, so great job guys!
We recently got new switches, and had been looking forward to Foreman
1.8 to start doing some more advanced networking. It's mostly working,
but we're still running into some rough edges.
In this particular scenario I'm setting up a CentOS 7 KVM hypervisor
(with latest updates as of somewhere this week). I used Foreman and a
slightly adapted version of the kickstart_networking_setup.erb snippet
to set up:
- eno1 as the provisioning interface
- eno2 and eno4 as bond0, which is the primary interface. We use
bonding mode 802.3ad.
So these are the four managed interfaces I have configured in
Foreman. eno3 gets autocreated (unmanaged) after the first puppet run,
but is not relevant further to the discussion.
I then use puppet-network
(https://forge.puppetlabs.com/razorsedge/network) to create a VLAN
interface on top of bond0 (bond0.3130) with a corresponding bridge
(br3130):
network::bridge { 'br3130':
ensure => 'up',
stp => true,
delay => '0',
}network::if::bridge { 'bond0.3130':
ensure => 'up',
bridge => 'br3130'
}This works, and the intention is that this bridge is used to connect
the virtual machines (also created by Foreman, and that works too,
great!). Note that on the hypervisor/host, neither the bridge nor the
VLAN interface has an IP address: this VLAN is intended only for the
guest VM's.
The problem is that after puppet runs, a number of interfaces get
autocreated (unmanaged):
- a second bond0 (Bond/virtual), with the current MAC address of the
bonding group (the original managed bond0 has no MAC address
configured).
- bond0.3130 (Bond/virtual): This isn't strictly speaking a bonding
interface. The VLAN ID is also not discovered. Not sure either of
these two should be considered a bug.
- br3130 (Interface/virtual)
See the screenshot foreman-autocreated-interfaces.png for an overview
The bug is that there are now two interfaces called "bond0", which is
invalid according to Foreman's model: whenever I now try to save the
host, I get an error for the unmanaged bond0: identifier bond0 has
already been taken (see foreman-bad-interface-bond0.png)
And what's worse: it's now even impossible to delete that duplicate
bond0 by hand: it disappears when I click the corresponding Delete
button, but when I click Submit to save the host, it re-appears, with
the same error. The only way out is to manually delete it from the
database (I'm probably going to install a cronjob for that as a
workaround).
It's a bit similar to the ticket created by my collegue Julien, but
the context here is somewhat more complex:
http://projects.theforeman.org/issues/10546
I've also attached the output of ifconfig and facter:
- facter.txt
- ifconfig.txt
Files
Updated by 
Updated by 
Updated by 
Updated by 
Updated by