In Foreman 1.20 we got a nice PR to add initial Facter 3 support.
However, a quick test shows facter doesn’t report the members of a team:
# facter networking
{
dhcp => "192.168.121.1",
domain => "example.com",
fqdn => "centos7-client-puppet5.example.com",
hostname => "centos7-client-puppet5",
interfaces => {
eth0 => {
bindings => [
{
address => "192.168.121.103",
netmask => "255.255.255.0",
network => "192.168.121.0"
}
],
bindings6 => [
{
address => "fe80::5054:ff:fe25:b4f0",
netmask => "ffff:ffff:ffff:ffff::",
network => "fe80::"
}
],
dhcp => "192.168.121.1",
ip => "192.168.121.103",
ip6 => "fe80::5054:ff:fe25:b4f0",
mac => "52:54:00:25:b4:f0",
mtu => 1500,
netmask => "255.255.255.0",
netmask6 => "ffff:ffff:ffff:ffff::",
network => "192.168.121.0",
network6 => "fe80::"
},
eth1 => {
dhcp => "192.168.122.1",
mac => "52:54:00:2d:65:6e",
mtu => 1500
},
eth2 => {
dhcp => "192.168.122.1",
mac => "52:54:00:2d:65:6e",
mtu => 1500
},
lo => {
bindings => [
{
address => "127.0.0.1",
netmask => "255.0.0.0",
network => "127.0.0.0"
}
],
bindings6 => [
{
address => "::1",
netmask => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
network => "::1"
}
],
ip => "127.0.0.1",
ip6 => "::1",
mtu => 65536,
netmask => "255.0.0.0",
netmask6 => "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
network => "127.0.0.0",
network6 => "::1"
},
team0 => {
bindings => [
{
address => "192.168.122.235",
netmask => "255.255.255.0",
network => "192.168.122.0"
}
],
bindings6 => [
{
address => "fe80::b0ea:7526:9b83:2a82",
netmask => "ffff:ffff:ffff:ffff::",
network => "fe80::"
}
],
dhcp => "192.168.122.1",
ip => "192.168.122.235",
ip6 => "fe80::b0ea:7526:9b83:2a82",
mac => "52:54:00:2d:65:6e",
mtu => 1500,
netmask => "255.255.255.0",
netmask6 => "ffff:ffff:ffff:ffff::",
network => "192.168.122.0",
network6 => "fe80::"
}
},
ip => "192.168.121.103",
ip6 => "fe80::5054:ff:fe25:b4f0",
mac => "52:54:00:25:b4:f0",
mtu => 1500,
netmask => "255.255.255.0",
netmask6 => "ffff:ffff:ffff:ffff::",
network => "192.168.121.0",
network6 => "fe80::",
primary => "eth0"
}
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:25:b4:f0 brd ff:ff:ff:ff:ff:ff
inet 192.168.121.103/24 brd 192.168.121.255 scope global noprefixroute dynamic eth0
valid_lft 3138sec preferred_lft 3138sec
inet6 fe80::5054:ff:fe25:b4f0/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master team0 state UP group default qlen 1000
link/ether 52:54:00:2d:65:6e brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master team0 state UP group default qlen 1000
link/ether 52:54:00:2d:65:6e brd ff:ff:ff:ff:ff:ff
7: team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 52:54:00:2d:65:6e brd ff:ff:ff:ff:ff:ff
inet 192.168.122.235/24 brd 192.168.122.255 scope global noprefixroute dynamic team0
valid_lft 3504sec preferred_lft 3504sec
inet6 fe80::b0ea:7526:9b83:2a82/64 scope link noprefixroute
valid_lft forever preferred_lft forever
# facter --version
3.11.4 (commit dc7babfd0ad4523a72d3366cd4f4322add9c3b4b)
Now I’m not familiar with teaming so maybe I didn’t do it right. However, I think this also doesn’t exist with bonding so perhaps we can treat them in the same way.