Hi,
We are seeing occasionally seeing issues with the teaming daemon not starting after a
reboot on centos 7 VMs. Here is an example from last night (from /var/log/messages.minor):
Oct 6 23:36:21 ****** ovs-ctl[623]: Starting ovsdb-server [ OK ]
Oct 6 23:36:22 ****** ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait --
init -- set Open_vSwitch . db-version=7.6.2
Oct 6 23:36:22 ****** ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl --no-wait set
Open_vSwitch . ovs-version=2.3.1
"external-ids:system-id=\"47ff9309-5609-47e0-819c-b9055b25edbb\""
"system-type=\"CentOS\""
"system-version=\"7.1.1503-Core\""
Oct 6 23:36:22 ****** ovs-ctl[623]: Configuring Open vSwitch system IDs [ OK ]
Oct 6 23:36:22 ****** network[733]: Bringing up loopback interface: [ OK ]
Oct 6 23:36:22 ****** kernel: [ 6.158533] gre: GRE over IPv4 demultiplexor driver
Oct 6 23:36:22 ****** systemd[1]: Starting system-teamd.slice.
Oct 6 23:36:22 ****** systemd[1]: Created slice system-teamd.slice.
Oct 6 23:36:22 ****** systemd[1]: Starting Team Daemon for device bond0...
Oct 6 23:36:22 ****** kernel: [ 6.199635] openvswitch: Open vSwitch switching
datapath
Oct 6 23:36:22 ****** ovs-ctl[623]: Inserting openvswitch module [ OK ]
Oct 6 23:36:22 ****** kernel: [ 6.338577] device ovs-system entered promiscuous mode
Oct 6 23:36:22 ****** kernel: [ 6.340086] openvswitch: netlink: Unknown key attribute
(type=62, max=21).
Oct 6 23:36:22 ****** kernel: [ 6.385293] device br-ex entered promiscuous mode
Oct 6 23:36:22 ****** kernel: [ 6.426511] device br-int entered promiscuous mode
Oct 6 23:36:22 ****** teamd[857]: Failed to get interface information list.
Oct 6 23:36:22 ****** teamd[857]: Failed to init interface information list.
Oct 6 23:36:22 ****** teamd[857]: Team init failed.
Oct 6 23:36:22 ****** teamd[857]: teamd_init() failed.
Oct 6 23:36:22 ****** teamd[857]: Failed: Invalid argument
Oct 6 23:36:22 ****** systemd[1]: teamd(a)bond0.service: main process exited, code=exited,
status=1/FAILURE
Oct 6 23:36:22 ****** network[733]: Bringing up interface bond0: Job for
teamd(a)bond0.service failed. See 'systemctl status teamd(a)bond0.service' and
'journalctl -xn' for details.
Oct 6 23:36:22 ****** kernel: [ 6.433515] device br-tun entered promiscuous mode
Oct 6 23:36:22 ****** systemd[1]: Unit teamd(a)bond0.service entered failed state.
Oct 6 23:36:22 ****** ovs-ctl[623]: Starting ovs-vswitchd [ OK ]
Oct 6 23:36:22 ****** network[733]: [FAILED]
Oct 6 23:36:22 ****** ovs-ctl[623]: Enabling remote OVSDB managers [ OK ]
Is this a known issue?
Chris
Show replies by date