Hi James,
The fix mentioned above fixes the issue for the 'dpif_netlink' module. The
problem mentioned
here is for the netdev_offload_tc. The fix should be basically the same though.
Erlon
** Changed in: openvswitch (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug no
This was fixed in the 2.13 branch under commit 1028cb71d0 which makes
the log level for these messages a lower priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897483
Title:
With hardware of
git tag --contains 1028cb71d0
v2.12.0
v2.12.1
v2.12.2
v2.12.3
v2.13.0
v2.13.1
v2.13.2
v2.13.3
v2.14.0
v2.14.1
v2.14.2
v2.15.0
** Changed in: openvswitch (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Triaging as enough there to confirm this is a bug and Medium as there is
a workaround.
** Changed in: openvswitch (Ubuntu)
Status: New => Triaged
** Changed in: openvswitch (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubunt
There is an indication in the below RHBZ this can actually prevent
openvswitch from working properly as it loses too much CPU time to this
processing in large environments (100s or 1000s of ports)
https://bugzilla.redhat.com/show_bug.cgi?id=1737982
Seems to be a rejected upstream patch here, uncl
Moved to openvswitch package as this is not a charm issue.
** Also affects: openvswitch (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-neutron-openvswitch
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
