Package: openvswitch / 2.10.7+ds1-0+deb10u1

Metadata

Package Version Patches format
openvswitch 2.10.7+ds1-0+deb10u1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
remove include debian automake.mk.patch | (download)

Makefile.am | 1 0 + 1 - 0 !
1 file changed, 1 deletion(-)

 remove debian/automake.mk
remove tests broken in mips64el and mipsel.patch | (download)

tests/ofproto-dpif.at | 26 0 + 26 - 0 !
1 file changed, 26 deletions(-)

 remove tests borken in mips64el and mipsel
 The first hunk fails in mips64el, the second on mipsel.
remove bfd decay tests.patch | (download)

tests/bfd.at | 143 0 + 143 - 0 !
1 file changed, 143 deletions(-)

 remove bfd decay
 This fails on armhf, probably because the platform is too slow.
disable failed tests.patch | (download)

tests/ovn.at | 3 0 + 3 - 0 !
1 file changed, 3 deletions(-)

 disable tests that are currently failing
 The issue was reported upstream.
py3 compat.patch | (download)

Makefile.am | 21 15 + 6 - 0 !
ovn/utilities/ovn-detrace.in | 20 11 + 9 - 0 !
python/ovstest/rpcserver.py | 16 4 + 12 - 0 !
python/ovstest/tcp.py | 4 2 + 2 - 0 !
python/ovstest/util.py | 4 1 + 3 - 0 !
python/ovstest/vswitch.py | 5 4 + 1 - 0 !
utilities/bugtool/ovs-bugtool.in | 22 11 + 11 - 0 !
utilities/ovs-check-dead-ifs.in | 8 5 + 3 - 0 !
utilities/ovs-dpctl-top.in | 18 10 + 8 - 0 !
utilities/ovs-l3ping.in | 12 7 + 5 - 0 !
utilities/ovs-parse-backtrace.in | 14 8 + 6 - 0 !
utilities/ovs-tcpdump.in | 2 2 + 0 - 0 !
utilities/ovs-tcpundump.in | 2 2 + 0 - 0 !
utilities/ovs-test.in | 39 21 + 18 - 0 !
utilities/ovs-vlan-test.in | 25 14 + 11 - 0 !
15 files changed, 117 insertions(+), 95 deletions(-)

 [patch] python 3 support

Misc fixes to Python based tooling for compatibility with
Python 2 and 3.

Signed-off-by: James Page <james.page@ubuntu.com>

use python3 m sphinx to build doc.patch | (download)

Documentation/automake.mk | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 using python3 -m sphinx to build doc
ovs dev ovs macros Make tests log how long they waited when they succeed..diff | (download)

tests/ovn.at | 15 8 + 7 - 0 !
tests/ovs-macros.at | 53 29 + 24 - 0 !
2 files changed, 37 insertions(+), 31 deletions(-)

---
removed tests which are failing in mips and armel.patch | (download)

tests/ofproto-dpif.at | 64 0 + 64 - 0 !
tests/ofproto.at | 209 0 + 209 - 0 !
2 files changed, 273 deletions(-)

 remove tests which are failing in mips and armel.
disable even more tests.patch | (download)

tests/ofproto-dpif.at | 87 0 + 87 - 0 !
tests/ofproto.at | 38 0 + 38 - 0 !
2 files changed, 125 deletions(-)

 disable even more tests
 These are failing in mipsel and mips64el
blacklist ofproto async msg ctrl of1.3 because of mips.patch | (download)

tests/ofproto.at | 115 0 + 115 - 0 !
1 file changed, 115 deletions(-)

 remove broken test on mips.
 Blacklist "ofproto - asynchronous message control (OpenFlow 1.3)" which
    fails on Mips arch.
remove yet another mips failing test.patch | (download)

tests/ovn.at | 202 0 + 202 - 0 !
1 file changed, 202 deletions(-)

 another test that's failing in mips
remove non deterministic tests.patch | (download)

tests/ovsdb-cluster.at | 33 0 + 33 - 0 !
1 file changed, 33 deletions(-)

 remove non-deterministic patches
 These tests are sometimes failing.
Fix_vswitchd_abort_when_a_port_is_added_and_the_controller_is_down.patch | (download)

ofproto/connmgr.c | 4 4 + 0 - 0 !
tests/bridge.at | 21 21 + 0 - 0 !
2 files changed, 25 insertions(+)

 connmgr: fix vswitchd abort when a port is added and the controller is down
 We see the below trace when a port is added to a bridge and the configured
 controller is down
 .
 0x00007fb002f8b207 in raise () from /lib64/libc.so.6
 0x00007fb002f8c8f8 in abort () from /lib64/libc.so.6
 0x00007fb004953026 in ofputil_protocol_to_ofp_version () from /lib64/libopenvswitch-2.10.so.0
 0x00007fb00494e38e in ofputil_encode_port_status () from /lib64/libopenvswitch-2.10.so.0
 0x00007fb004ef1c5b in connmgr_send_port_status () from /lib64/libofproto-2.10.so.0
 0x00007fb004efa9f4 in ofport_install () from /lib64/libofproto-2.10.so.0
 0x00007fb004efbfb2 in update_port () from /lib64/libofproto-2.10.so.0
 0x00007fb004efc7f9 in ofproto_port_add () from /lib64/libofproto-2.10.so.0
 0x0000556d540a3f95 in bridge_add_ports__ ()
 0x0000556d540a5a47 in bridge_reconfigure ()
 0x0000556d540a9199 in bridge_run ()
 0x0000556d540a02a5 in main ()
 .
 The abort is because of ofputil_protocol_to_ofp_version() is called with invalid
 protocol - OFPUTIL_P_NONE. Please see [1] for more details. Similar aborts are
 seen as reported in [2].
 .
 The commit [3] changed the behavior of the function rconn_get_version().
 Before the commit [3], the function ofconn_receives_async_msg() would always
 return false if the connection to the controller was down, since
 rconn_get_version() used to return -1. This patch now checks the rconn
 connection status in ofconn_receives_async_msg() and returns false if not
 connected. This would avoid the aborts seen in the above stack trace.
 .
 The issue can be reproduced by running the test added in this patch
 without the fix.
 .
 [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1640045
 [2] - https://bugzilla.redhat.com/show_bug.cgi?id=1637926
 .
 [3] - 476d2551ab ("rconn: Introduce new invariant to fix assertion failure in corner case.")
Signed-off-by: Numan Siddique <nusiddiq@redhat.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>