5.0 Helm: DPDK - On deleting vrouter chart, interfaces are not binded back to host
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
New
|
High
|
alexey-mr | |||
Trunk |
New
|
High
|
alexey-mr |
Bug Description
On a Helm after deleting a vrouter chart with dpdk, the nics are not rebinded back to the host
While this is not a problem with a successful install, in-case of failures or when user delete's and
and deploys a the chart , it wil fails as physical interface is not available on the host
root@cmbu-
Network devices using DPDK-compatible driver
=======
0000:81:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=uio_pci_generic unused=ixgbe
0000:81:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=uio_pci_generic unused=ixgbe
Network devices using kernel driver
=======
0000:02:00.0 '82598EB 10-Gigabit AT CX4 Network Connection' if=p2p1 drv=ixgbe unused=
0000:02:00.1 '82598EB 10-Gigabit AT CX4 Network Connection' if=p2p2 drv=ixgbe unused=
0000:05:00.0 'I350 Gigabit Network Connection' if=enp5s0f0 drv=igb unused=
0000:05:00.1 'I350 Gigabit Network Connection' if=enp5s0f1 drv=igb unused=
0000:05:00.2 'I350 Gigabit Network Connection' if=enp5s0f2 drv=igb unused=
0000:05:00.3 'I350 Gigabit Network Connection' if=enp5s0f3 drv=igb unused=
Other network devices
=======
<none>
Workaround:
copy the dpdk_nick_bind.py to host
./dpdk_nic_bind.py --force --bind=ixgbe 0000:81:00.0
./dpdk_nic_bind.py --force --bind=ixgbe 0000:81:00.1
ifdown and ifup of the interface
summary: |
- 5.0 Heml: On deleting vrouter chart, interfaces are not binded back to - host + 5.0 Heml: DPDK - On deleting vrouter chart, interfaces are not binded + back to host |
Changed in juniperopenstack: | |
milestone: | none → r5.0.0 |
summary: |
- 5.0 Heml: DPDK - On deleting vrouter chart, interfaces are not binded + 5.0 Helm: DPDK - On deleting vrouter chart, interfaces are not binded back to host |
information type: | Proprietary → Public |