datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
Yakkety |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned | ||
openvswitch (Ubuntu) |
Invalid
|
Undecided
|
Taco Screen team | ||
Yakkety |
Invalid
|
Undecided
|
Unassigned | ||
Zesty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
---Problem Description---
Recreate and error info:
Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from
the Ubuntu 4.4 kernel.
Iperf was used to send traffic between client VMs over VXLAN. The
traffic did still flow, but every packet had to go to user space due to
the flow creation failures, which drastically impacted performance and
cpu utilization.
When using VXLAN, the following error is showing up in dmesg
openvswitch: netlink: Unknown IP tunnel attribute 14
Also there are tons of these errors in the openvswitch log
2017-03-
failed to put[create] (Invalid argument)
ufid:2d1a9aeb-
Debug showed that this attribute, OVS_TUNNEL_
seen in the switch statement in method, static int ip_tun_from_nlattr,
in flow_netlink.c . Because there is no case for this attribute, the
default is hit and returns an error.
The issue was first seen using the packages in the Ubuntu 4.8 kernel,
which is OVS 2.5. OVS 2.6 and 2.6.1 were also tried with the kernel
packages and the same issue was seen. Tried building OVS 2.7 and
loading the openvswitch-
the issue persisted. The proposed patch seems to eliminate the error
messages and also fixed the segmentation and performance issues that
were seen.
---uname output---
stock 4.8 kernel
Machine Type = p8
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from
the Ubuntu 4.4 kernel.
Iperf was used to send traffic between client VMs over VXLAN. The
traffic did still flow, but every packet had to go to user space due to
the flow creation failures, which drastically impacted performance and
cpu utilization.
When using VXLAN, the following error is showing up in dmesg
openvswitch: netlink: Unknown IP tunnel attribute 14
Link to the patch is https:/
tags: |
added: targetmilestone-inin16042 removed: targetmilestone-inin1610 |
Changed in linux (Ubuntu Yakkety): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Zesty): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Yakkety): | |
assignee: | Canonical Kernel Team (canonical-kernel-team) → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Zesty): | |
assignee: | Canonical Kernel Team (canonical-kernel-team) → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Zesty): | |
status: | In Progress → Fix Released |
Changed in linux (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in ubuntu-power-systems: | |
status: | New → In Progress |
Changed in linux (Ubuntu Yakkety): | |
status: | In Progress → Fix Committed |
Changed in ubuntu-power-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-power-systems: | |
status: | Fix Committed → Fix Released |
tags: |
added: verification-done-yakkety removed: verification-needed-yakkety |
tags: |
added: targetmilestone-inin1610 removed: targetmilestone-inin16042 |
Default Comment by Bridge