-
Bug
-
Resolution: Done
-
Normal
-
None
-
1
-
False
-
-
False
-
?
-
?
-
?
-
No
-
-
Bug Fix
-
Done
-
Automated
-
-
-
Rejected
-
Important
Having applied this ovs_user_bridge configration:
- type: ovs_user_bridge name: br-link0 use_dhcp: false ovs_extra: "set port br-link0 tag={{ lookup('vars', networks_lower['tenant'] ~ '_vlan_id') }}" addresses: - ip_netmask: {{ lookup('vars', networks_lower['tenant'] ~ '_ip') }}/{{ lookup('vars', networks_lower['tenant'] ~ '_cidr')}} members: - type: ovs_dpdk_bond name: dpdkbond0 mtu: 9000 rx_queue: 1 members: - type: ovs_dpdk_port driver: mlx5_core name: dpdk1 members: - type: interface name: nic6
We can see the bond port is missing:
[root@compute-1 cloud-admin]# ovs-vsctl show f0250adf-e99a-4040-af85-1be309be235a Manager “ptcp:6640:127.0.0.1” is_connected: true Bridge br-link0 fail_mode: standalone datapath_type: netdev Port br-link0 tag: 204 Interface br-link0 type: internal
Due to this error:
[root@compute-1 cloud-admin]# ifup dpdkbond0 WARN : [ifup] You are using ‘ifup’ script provided by ‘network-scripts’, which are now deprecated. WARN : [ifup] ‘network-scripts’ will be removed from distribution in near future. WARN : [ifup] It is advised to switch to ‘NetworkManager’ instead - it provides ‘ifup/ifdown’ scripts as well. ovs-vsctl: ‘add-bond’ command requires at least 4 arguments [root@compute-1 cloud-admin]# ovs-vsctl add-bond br-link0 dpdkbond dpdk1 \ -- set Interface dpdk1 type=dpdk options:dpdk-devargs=0000:41:00.1 ovs-vsctl: ‘add-bond’ command requires at least 4 arguments