Detailed bug description:
After rebooting compute node one of dpdk interface belonging to balance-tcp bonding mode is lost.
ovs-vsctl show:
Bridge br-prv
Controller "tcp:127.0.0.1:6633" is_connected: true
fail_mode: secure
Port "bond0" Interface "dpdk1" type: dpdk error: "could not open network device dpdk1 (No such device)" Interface "dpdk0" type: dpdk
Port br-prv Interface br-prv type: internal
Port phy-br-prv Interface phy-br-prv type: patch options: {peer=int-br-prv}
ovs_version: "2.6.1"
Steps to reproduce:
1. Deploy cluster with dpdk and bond mode balance-tcp. (In my case I used 2 compute nodes)
2. Configure LACP in ovs and on the hardware switch
ovs-vsctl set port bond0 lacp=active
ovs-vsctl set port bond0 other_config:lacp-time=slow
3. Check that LACP in negotiated
root@node-3:~# ovs-appctl bond/show bond0
---- bond0 ----
bond_mode: balance-tcp
bond may use recirculation: yes, Recirc-ID : 1 bond-hash-basis: 0
updelay: 3000 ms
downdelay: 1000 ms
next rebalance: 7774 ms lacp_status: `negotiated`
active slave mac: 00:25:90:0a:4b:dc(dpdk0)
2. Reboot any compute node
3. Look at port status in ovs
ovs-vsctl show
Expected results:
LACP works correctly.
Actual result:
Could not open network device dpdk0 or 1. Only one interface is available
Reproducibility:
Checked on builds 1499, 1507,1513. Each time after rebooting compute node.
Description of the environment:
Fuel 10 build 1513
1 controller, 2 computes, 1 BASE-OS node. Bonding 2x10G on both compute nodes with DPDK and balance-tcp mode.
Detailed bug description:
After rebooting compute node one of dpdk interface belonging to balance-tcp bonding mode is lost.
ovs-vsctl show:
Bridge br-prv 0.0.1:6633"
is_ connected: true
Interface "dpdk1"
type: dpdk
error: "could not open network device dpdk1 (No such device)"
Interface "dpdk0"
type: dpdk
Interface br-prv
type: internal
Interface phy-br-prv
type: patch
options: {peer=int-br-prv}
Controller "tcp:127.
fail_mode: secure
Port "bond0"
Port br-prv
Port phy-br-prv
ovs_version: "2.6.1"
Steps to reproduce:
1. Deploy cluster with dpdk and bond mode balance-tcp. (In my case I used 2 compute nodes)
2. Configure LACP in ovs and on the hardware switch
ovs-vsctl set port bond0 lacp=active lacp-time= slow
ovs-vsctl set port bond0 other_config:
3. Check that LACP in negotiated
---- bond0 ----
bond_mode: balance-tcp
bond may use recirculation: yes, Recirc-ID : 1
updelay: 3000 ms
downdelay: 1000 ms
next rebalance: 7774 ms
active slave mac: 00:25:90:
2. Reboot any compute node
3. Look at port status in ovs
ovs-vsctl show
Expected results:
LACP works correctly.
Actual result:
Could not open network device dpdk0 or 1. Only one interface is available
Reproducibility:
Checked on builds 1499, 1507,1513. Each time after rebooting compute node.
Description of the environment:
Fuel 10 build 1513
1 controller, 2 computes, 1 BASE-OS node. Bonding 2x10G on both compute nodes with DPDK and balance-tcp mode.
Additional information:
root@node-1:~# dpdk-devbind -s
Network devices using DPDK-compatible driver ======= ======= ======= ======= ======= ==
=======
0000:03:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe
0000:03:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=ixgbe
Network devices using kernel driver ======= ======= ======= ======= ens11f0d1 drv=i40e unused=igb_uio ens11f1d1 drv=i40e unused=igb_uio
=======
0000:0a:00.0 'I350 Gigabit Network Connection' if=enp10s0f0 drv=igb unused=igb_uio
0000:0a:00.1 'I350 Gigabit Network Connection' if=enp10s0f1 drv=igb unused=igb_uio
0000:81:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens11f0,
0000:81:00.1 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens11f1,
Fuel diagnostic snapshot: