os-net-config fails on 2nd run with DPDK net config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-net-config |
Fix Released
|
High
|
Saravanan KR | ||
tripleo |
Fix Released
|
High
|
Saravanan KR |
Bug Description
When os-net-config is called for the 2nd time during a compute node deployment with below nic config added to the compute.yaml, it fails with processutils.
-
type: ovs_user_bridge
name: br-link
-
This is because if the interface is already bound to DPDK driver, ethtool will not be able to find the interface. On the first run, os-net-config configures it successfully and on the 2nd run, os-net-config throws exception.
And if the nic configs has nic numbering, with mixed interfaces, like DPDK and non-DPDK interfaces, if the non-DPDK interfaces are added after DPDK interfaces, like
nic1 - DPDK
nic2 - non-DPDK
then on the second run, DPDK nic will NOT be found, so the active nic list will change on the 2nd run.
Changed in tripleo: | |
assignee: | nobody → Saravanan KR (skramaja) |
status: | New → In Progress |
description: | updated |
affects: | tripleo → os-net-config |
affects: | os-net-config → tripleo |
affects: | tripleo → os-net-config |
Changed in os-net-config: | |
importance: | Undecided → High |
Changed in tripleo: | |
assignee: | nobody → Saravanan KR (skramaja) |
status: | New → In Progress |
Changed in tripleo: | |
milestone: | none → newton-rc2 |
Changed in tripleo: | |
importance: | Undecided → High |
Changed in tripleo: | |
status: | In Progress → Fix Released |
Review posted - https:/ /review. openstack. org/#/c/ 364354/