[Bug 2063152] Re: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints
** Tags removed: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063152 Title: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066908] [NEW] [SRU] ovn 24.03.2 point release
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. The update contains the following package updates: * ovn 24.03.2 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. ** Affects: ovn (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ovn (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066908 Title: [SRU] ovn 24.03.2 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2066908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063112] Re: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed
** Tags removed: block-proposed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063112 Title: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066906] [NEW] [noble] Missing fix for continuations with associated metering.
Public bug reported: [ Impact ] There is a bug in Open vSwitch which is required for successful build and test run for OVN 24.03.2. [ Test plan ] Build and test the OVN 24.03.2 package. [ Regression Potential ] Minimal, the fix has been available for some time upstream already and has been deemed safe to backport all the way to Open vSwitch 2.17 by the upstream maintainers. [ Other Info ] The bug has been fixed upstream, and there is a patch available for branch-3.3 [0]. 0: https://github.com/openvswitch/ovs/commit/c560f6ca3257dd3b64e01a4a244b02b90216858b ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: Invalid ** Affects: openvswitch (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: openvswitch (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066906 Title: [noble] Missing fix for continuations with associated metering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2066906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066194] [NEW] flaky test: ovn-controller update network name option for localnet port
Public bug reported:
Full log:
https://buildd.debian.org/status/fetch.php?pkg=ovn=riscv64=24.03.2-1=1716223822=0
The actual test appears to succeed, but in some situations ovs-vswitchd will
log a WARN during teardown:
./ovn.at:35715: check_logs "
$error
/connection failed (No such file or directory)/d
/has no network name*/d
/receive tunnel port not found*/d
/Failed to locate tunnel to reach main chassis/d
/Transaction causes multiple rows.*MAC_Binding/d
" $sbox
--- /dev/null 2024-05-19 10:34:30.13200 +
+++ /<>/tests/testsuite.dir/at-groups/485/stdout 2024-05-20
16:49:57.83125 +
@@ -0,0 +1 @@
+2024-05-20T16:49:56.722Z|00307|ofproto_dpif_xlate|WARN|received packet on
unknown port 2 on bridge br-phys-1 while processing
arp,in_port=CONTROLLER,vlan_tci=0x,dl_src=00:00:00:00:00:01,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=10.0.0.1,arp_tpa=10.0.0.1,arp_op=1,arp_sha=00:00:00:00:00:01,arp_tha=00:00:00:00:00:00
To me this looks benign, and I suggest we just ignore this warning
during tear down.
# -*- compilation -*-
485. ovn.at:35715: testing ovn-controller update network_name option for
localnet port -- parallelization=yes -- ovn_monitor_all=yes ...
creating ovn-sb database
ovsdb-server -vjsonrpc
--remote=punix:/<>/tests/testsuite.dir/485/ovn-sb/ovn-sb.sock
--remote=db:OVN_Southbound,SB_Global,connections
--private-key=/<>/tests/testpki-test-privkey.pem
--certificate=/<>/tests/testpki-test-cert.pem
--ca-cert=/<>/tests/testpki-cacert.pem
/<>/tests/testsuite.dir/485/ovn-sb/ovn-sb.db -vconsole:off
--detach --no-chdir --pidfile --log-file
creating ovn-nb database
ovsdb-server -vjsonrpc
--remote=punix:/<>/tests/testsuite.dir/485/ovn-nb/ovn-nb.sock
/<>/tests/testsuite.dir/485/ovn-nb/ovn-nb.db -vconsole:off
--detach --no-chdir --pidfile --log-file
starting northd
ovn-northd --n-threads=4 -vjsonrpc
--ovnnb-db=unix:/<>/tests/testsuite.dir/485/ovn-nb/ovn-nb.sock
--ovnsb-db=unix:/<>/tests/testsuite.dir/485/ovn-sb/ovn-sb.sock
-vconsole:off --detach --no-chdir --pidfile --log-file
2024-05-20T16:49:52Z|1|ovn_northd|INFO|Using 4 threads
e573e254-3fd9-4150-a064-5e2856bbe85b
ovn-macros.at:311: waiting until TCP_PORT=`sed -n 's/.*0:.*: listening on port
\([0-9]*\)$/\1/p' "$d/ovn-sb/ovsdb-server.log"` && test X != X"$TCP_PORT"...
ovn-macros.at:311: wait succeeded immediately
adding simulator 'main'
ovsdb-server
--remote=punix:/<>/tests/testsuite.dir/485/main/db.sock
-vconsole:off --detach --no-chdir --pidfile --log-file
ovs-vswitchd --enable-dummy=system -vvconn -vofproto_dpif -vunixctl
-vconsole:off --detach --no-chdir --pidfile --log-file
adding simulator 'hv1'
ovsdb-server
--remote=punix:/<>/tests/testsuite.dir/485/hv1/db.sock
-vconsole:off --detach --no-chdir --pidfile --log-file
ovs-vswitchd --enable-dummy=system -vvconn -vofproto_dpif -vunixctl
-vconsole:off --detach --no-chdir --pidfile --log-file
ovs-vsctl add-br br-int
./ovn-macros.at:534: "$@"
ovs-vsctl add-br br-int-2
./ovn-macros.at:534: "$@"
ovs-vsctl add-br br-phys-1
./ovn-macros.at:534: "$@"
ovs-vsctl add-br br-phys-2
./ovn-macros.at:534: "$@"
ovs-vsctl add-br br-phys-3
./ovn-macros.at:534: "$@"
ovs-vsctl set open .
external-ids:ovn-bridge-mappings-hv1=phys-1:br-phys-1,phy-2:br-phys-2,phys-3:br-phys-3
./ovn-macros.at:534: "$@"
ovn-controller --enable-dummy-vif-plug -vconsole:off --detach --no-chdir
--pidfile --log-file
ovs-vsctl: no key "ovn-encap-type-hv1" in Open_vSwitch record "." column
external_ids
ovs-vsctl: no key "ovn-encap-ip-hv1" in Open_vSwitch record "." column
external_ids
Waiting until ip in sb Encap with chassis_name=hv1 type=geneve is 192.168.1.1...
ovn-macros.at:639: waiting until
found=$(ovn-${db}ctl --bare --columns $column find $table $a $b $c $d $e)
found=$(for d in $found; do echo $d; done | sort)
test "$expected" = "$found"
...
ovn-macros.at:639: wait succeeded immediately
Waiting until ip in sb Encap with chassis_name=hv1 type=vxlan is 192.168.1.1...
ovn-macros.at:639: waiting until
found=$(ovn-${db}ctl --bare --columns $column find $table $a $b $c $d $e)
found=$(for d in $found; do echo $d; done | sort)
test "$expected" = "$found"
...
ovn-macros.at:639: wait succeeded immediately
ovs-vsctl -- add-port br-int vif1 -- set interface vif1
external-ids:iface-id=lp1
./ovn-macros.at:534: "$@"
ovn-nbctl ls-add ls
./ovn-macros.at:534: "$@"
ovn-nbctl lsp-add ls lp1
./ovn-macros.at:534: "$@"
ovn-nbctl lsp-set-addresses lp1 00:00:00:00:00:01 10.0.0.1
./ovn-macros.at:534: "$@"
ovn-nbctl lsp-add ls ln_port
./ovn-macros.at:534: "$@"
ovn-nbctl lsp-set-addresses ln_port unknown
./ovn-macros.at:534: "$@"
ovn-nbctl lsp-set-type ln_port localnet
./ovn-macros.at:534: "$@"
ovn-nbctl lsp-set-options ln_port network_name=phys-1
./ovn-macros.at:534: "$@"
Waiting until 0 rows in nb Logical_Switch_Port with up!=true type=""...
ovn-macros.at:585: waiting until test $count = $(count_rows
[Bug 2059097] Re: [SRU] ovn 22.03.7 point release
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-fnordahl-sru/jammy/amd64/o/ovn/20240517_171752_56ea5@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-fnordahl-sru/jammy/arm64/o/ovn/20240513_010358_3e1c0@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-fnordahl-sru/jammy/ppc64el/o/ovn/20240515_211959_93561@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-fnordahl-sru/jammy/s390x/o/ovn/20240515_022420_d0233@/log.gz ** Changed in: ovn (Ubuntu Jammy) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059097 Title: [SRU] ovn 22.03.7 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2059097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065563] Re: [ovn-vif] Issue with connecting PF representor of DPU to OVN
** Changed in: ovn (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065563 Title: [ovn-vif] Issue with connecting PF representor of DPU to OVN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2065563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065269] [NEW] [ovn 22.03] unstable test - ACL after lb - reject
Public bug reported: This appears to be addressed by https://github.com/ovn- org/ovn/commit/796d38a3b8dade81bffe6794b62b1b44267d362c Log excerpt: 5058s ## ## 5058s ## Summary of the failures. ## 5058s ## ## 5058s Failed tests: 5058s ovn 22.03.7 test suite test groups: 5058s 5058s NUM: FILE-NAME:LINE TEST-GROUP-NAME 5058s KEYWORDS 5058s 5058s 245: system-ovn.at:5093 ACL after lb - reject -- ovn-northd -- dp-groups=no -- parallelization=yes -- ovn_monitor_all=yes 5058s lb 5058s 247: system-ovn.at:5093 ACL after lb - reject -- ovn-northd -- dp-groups=no -- parallelization=no -- ovn_monitor_all=yes 5058s lb 5058s 5058s ## -- ## 5058s ## Detailed failed tests. ## 5058s ## -- ## 5058s 5058s # -*- compilation -*- 5058s 245. system-ovn.at:5093: testing ACL after lb - reject -- ovn-northd -- dp-groups=no -- parallelization=yes -- ovn_monitor_all=yes ... 5058s creating ovn-sb database 5058s ovsdb-server -vjsonrpc --remote=punix:/tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovn-sb/ovn-sb.sock --remote=db:OVN_Southbound,SB_Global,connections --private-key=/tmp/autopkgtest.VPohev/build.6er/src/tests/testpki-test-privkey.pem --certificate=/tmp/autopkgtest.VPohev/build.6er/src/tests/testpki-test-cert.pem --ca-cert=/tmp/autopkgtest.VPohev/build.6er/src/tests/testpki-cacert.pem /tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovn-sb/ovn-sb.db -vconsole:off --detach --no-chdir --pidfile --log-file 5058s creating ovn-nb database 5058s ovsdb-server -vjsonrpc --remote=punix:/tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovn-nb/ovn-nb.sock /tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovn-nb/ovn-nb.db -vconsole:off --detach --no-chdir --pidfile --log-file 5058s starting northd 5058s ovn-northd -vjsonrpc --ovnnb-db=unix:/tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovn-nb/ovn-nb.sock --ovnsb-db=unix:/tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovn-sb/ovn-sb.sock -vconsole:off --detach --no-chdir --pidfile --log-file 5058s 9e0e544d-ff8c-4190-bf4d-1e9d9b707f8a 5058s ovn-macros.at:234: waiting until TCP_PORT=`sed -n 's/.*0:.*: listening on port \([0-9]*\)$/\1/p' "$d/ovn-sb/ovsdb-server.log"` && test X != X"$TCP_PORT"... 5058s ovn-macros.at:234: wait succeeded immediately 5058s ./system-ovn.at:5093: modprobe openvswitch 5058s Module vport_lisp not loaded. 5058s Module vport_stt not loaded. 5058s ./system-ovn.at:5093: ovsdb-tool create conf.db $ovs_srcdir/vswitchd/vswitch.ovsschema 5058s ./system-ovn.at:5093: ovsdb-server --detach --no-chdir --pidfile --log-file --remote=punix:$OVS_RUNDIR/db.sock 5058s stderr: 5058s 2024-04-28T07:47:46Z|1|vlog|INFO|opened log file /tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovsdb-server.log 5058s ./system-ovn.at:5093: sed < stderr ' 5058s /vlog|INFO|opened log file/d 5058s /ovsdb_server|INFO|ovsdb-server (Open vSwitch)/d' 5058s ./system-ovn.at:5093: ovs-vsctl --no-wait init 5058s ./system-ovn.at:5093: ovs-vswitchd --detach --no-chdir --pidfile --log-file -vvconn -vofproto_dpif -vunixctl 5058s stderr: 5058s 2024-04-28T07:47:46Z|1|vlog|INFO|opened log file /tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/ovs-vswitchd.log 5058s 2024-04-28T07:47:46Z|2|ovs_numa|INFO|Discovered 4 CPU cores on NUMA node 0 5058s 2024-04-28T07:47:46Z|3|ovs_numa|INFO|Discovered 1 NUMA nodes and 4 CPU cores 5058s 2024-04-28T07:47:46Z|4|reconnect|INFO|unix:/tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/db.sock: connecting... 5058s 2024-04-28T07:47:46Z|5|reconnect|INFO|unix:/tmp/autopkgtest.VPohev/build.6er/src/tests/system-kmod-testsuite.dir/245/db.sock: connected 5058s ./system-ovn.at:5093: sed < stderr ' 5058s /ovs_numa|INFO|Discovered /d 5058s /vlog|INFO|opened log file/d 5058s /vswitchd|INFO|ovs-vswitchd (Open vSwitch)/d 5058s /reconnect|INFO|/d 5058s /dpif_netlink|INFO|Generic Netlink family .ovs_datapath. does not exist/d 5058s /ofproto|INFO|using datapath ID/d 5058s /netdev_linux|INFO|.*device has unknown hardware address family/d 5058s /ofproto|INFO|datapath ID changed to fedcba9876543210/d 5058s /dpdk|INFO|DPDK Disabled - Use other_config:dpdk-init to enable/d 5058s /netlink_socket|INFO|netlink: could not enable listening to all nsid/d 5058s /netdev: Flow API/d 5058s /probe tc:/d 5058s /tc: Using policy/d' 5058s ./system-ovn.at:5093: ovs-vsctl -- add-br br0 -- set Bridge br0 protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13,OpenFlow14,OpenFlow15 fail-mode=secure -- 5058s ovn-controller -vconsole:off --detach --no-chdir --pidfile --log-file 5058s ./system-ovn.at:5093: ovn_populate_arp__ 5058s stdout: 5058s Cannot remove namespace file "/run/netns/sw0-p1-rej": No
[Bug 2063112] Re: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed
** Changed in: openvswitch (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063112 Title: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063112] Re: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240501_021126_e862b@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/o/openvswitch/20240501_021215_8ac01@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/o/openvswitch/20240501_014114_7b2c4@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/o/openvswitch/20240501_014529_fcfa6@/log.gz ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063112 Title: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063152] Re: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240501_021126_e862b@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/o/openvswitch/20240501_021215_8ac01@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/o/openvswitch/20240501_014114_7b2c4@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/o/openvswitch/20240501_014529_fcfa6@/log.gz ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063152 Title: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063408] [NEW] [debian] FTBFS on 'testing SSL db: implementation'
Public bug reported:
Full log:
https://salsa.debian.org/fnordahl/openvswitch/-/jobs/5634791/raw
# -*- compilation -*-
1890. ovsdb-server.at:827: testing SSL db: implementation ...
0
../../tests/ovsdb-server.at:847: ovsdb-tool create db schema
stderr:
stdout:
../../tests/ovsdb-server.at:850: ovsdb-tool transact db \
'["mydb",
{"op": "insert",
"table": "SSL",
"row": {"private_key": "'"$PKIDIR/testpki-privkey2.pem"'",
"certificate": "'"$PKIDIR/testpki-cert2.pem"'",
"ca_cert": "'"$PKIDIR/testpki-cacert.pem"'",
"ssl_protocols": "'"TLSv1.2,TLSv1.1"'",
"ssl_ciphers":
"'"HIGH:!aNULL:!MD5:!ECDHE-ECDSA-AES256-GCM-SHA384"'"}}]'
stderr:
stdout:
[{"uuid":["uuid","dba74f11-4ff1-4e6d-bf0b-d5115e4cd84d"]}]
../../tests/ovsdb-server.at:862: ovsdb-server --log-file --detach --no-chdir
--pidfile \
--private-key=db:mydb,SSL,private_key \
--certificate=db:mydb,SSL,certificate \
--ca-cert=db:mydb,SSL,ca_cert \
--ssl-protocols=db:mydb,SSL,ssl_protocols \
--ssl-ciphers=db:mydb,SSL,ssl_ciphers \
--remote=pssl:0:127.0.0.1 db
stderr:
2024-04-24T07:46:57Z|1|vlog|INFO|opened log file
/builds/fnordahl/openvswitch/debian/output/source_dir/_debian/tests/testsuite.dir/1890/ovsdb-server.log
2024-04-24T07:46:57Z|2|socket_util|INFO|0:127.0.0.1: listening on port 38763
stdout:
ovsdb-server.at:871: waiting until SSL_PORT=`sed -n 's/.*0:.*: listening on
port \([0-9]*\)$/\1/p' "ovsdb-server.log"` && test X != X"$SSL_PORT"...
ovsdb-server.at:871: wait succeeded immediately
../../tests/ovsdb-server.at:872: ovsdb-client \
--private-key=$PKIDIR/testpki-privkey.pem \
--certificate=$PKIDIR/testpki-cert.pem \
--ca-cert=$PKIDIR/testpki-cacert.pem \
--ssl-protocols=TLSv1.2,TLSv1.1 \
--ssl-ciphers=HIGH:!aNULL:!MD5 \
transact ssl:127.0.0.1:$SSL_PORT \
'["mydb",
{"op": "select",
"table": "SSL",
"where": [],
"columns": ["private_key"]}]'
stderr:
stdout:
[{"rows":[{"private_key":"/builds/fnordahl/openvswitch/debian/output/source_dir/_debian/tests/testpki-privkey2.pem"}]}]
../../tests/ovsdb-server.at:887: cat output
stderr:
../../tests/ovsdb-server.at:893: ovsdb-client \
--private-key=$PKIDIR/testpki-privkey.pem \
--certificate=$PKIDIR/testpki-cert.pem \
--ca-cert=$PKIDIR/testpki-cacert.pem \
--ssl-protocols=TLSv1 \
--ssl-ciphers=HIGH:!aNULL:!MD5 \
transact ssl:127.0.0.1:$SSL_PORT \
'["mydb",
{"op": "select",
"table": "SSL",
"where": [],
"columns": ["private_key"]}]'
stderr:
2024-04-24T07:46:57Z|1|stream_ssl|WARN|SSL_connect: error:0ABF:SSL
routines::no protocols available
ovsdb-client: failed to connect to "ssl:127.0.0.1:38763" (Protocol error)
stdout:
../../tests/ovsdb-server.at:909: sed -n "/failed to connect/s/ (.*)//p" output
stderr:
../../tests/ovsdb-server.at:916: ovsdb-client \
--private-key=$PKIDIR/testpki-privkey.pem \
--certificate=$PKIDIR/testpki-cert.pem \
--ca-cert=$PKIDIR/testpki-cacert.pem \
--ssl-protocols=TLSv1.2,TLSv1.1 \
--ssl-ciphers=ECDHE-ECDSA-AES256-GCM-SHA384 \
transact ssl:127.0.0.1:$SSL_PORT \
'["mydb",
{"op": "select",
"table": "SSL",
"where": [],
"columns": ["private_key"]}]'
stderr:
2024-04-24T07:46:57Z|1|stream_ssl|WARN|SSL_connect: error:0A000410:SSL
routines::ssl/tls alert handshake failure
ovsdb-client: failed to connect to "ssl:127.0.0.1:38763" (Protocol error)
stdout:
../../tests/ovsdb-server.at:932: sed -n "/failed to connect/s/ (.*)//p" output
stderr:
../../tests/ovsdb-server.at:939: grep "sslv3 alert handshake failure" output
stderr:
stdout:
../../tests/ovsdb-server.at:939: exit code was 1, expected 0
1890. ovsdb-server.at:827: 1890. SSL db: implementation (ovsdb-server.at:827):
FAILED (ovsdb-server.at:939)
** Affects: openvswitch (Ubuntu)
Importance: Undecided
Assignee: Frode Nordahl (fnordahl)
Status: In Progress
** Summary changed:
- [debian] build fails on 'testing SSL db: implementation'
+ [debian] FTBFS on 'testing SSL db: implementation'
** Changed in: openvswitch (Ubuntu)
Assignee: (unassigned) => Frode Nordahl (fnordahl)
** Changed in: openvswitch (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063408
Title:
[debian] FTBFS on 'testing SSL db: implementation'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063408/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063112] Re: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-fnordahl-ovn-dev/noble/amd64/o/openvswitch/20240423_081507_2901a@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble-fnordahl-ovn-dev/noble/arm64/o/openvswitch/20240424_110838_8ed1f@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble-fnordahl-ovn-dev/noble/s390x/o/openvswitch/20240424_092618_1acc9@/log.gz ** Description changed: - In bug 2059400 we switch to using 1G hugepages on arm64, as 2M hugepages - does not work. For the OVN autopkgtests using 1 1G hugepage per NUNMA - node is sufficient, but for the openvswitch autopkgtests that is not - enough for all tests to succeed. + [ Impact ] + The autopkgtest for openvswitch on arm64 currently always fails, which prevents us from catching any real architecture specific regressions as dependencies are updated in the stable release. + + [ Test Plan ] + Trigger autopkgtest runs against PPA and document their output / result. + + [ Regression Potential ] + As this is a test-only change, I'd say none for the actual end user consumption of the package. + + For CI stability however, the issue appears to have been present + throughout the development phase of Noble, so there may be test cases + with architecture specific flakiness which has yet to be uncovered. + Rest assured, we will follow up with any required updates if they do + appear. + + [ Other Info ] + In bug 2059400 we switch to using 1G hugepages on arm64, as 2M hugepages does not work. For the OVN autopkgtests using 1 1G hugepage per NUNMA node is sufficient, but for the openvswitch autopkgtests that is not enough for all tests to succeed. Bump number of 1G hugepages for the openvswitch autopkgtest. ** Also affects: openvswitch (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063112 Title: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063152] Re: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-fnordahl-ovn-dev/noble/amd64/o/openvswitch/20240423_081507_2901a@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble-fnordahl-ovn-dev/noble/arm64/o/openvswitch/20240424_110838_8ed1f@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble-fnordahl-ovn-dev/noble/s390x/o/openvswitch/20240424_092618_1acc9@/log.gz ** Description changed: - There is an issue with running the DPDK tests on arm64 which is - currently worked around by using 1G hugepages as opposed to 2M hugepages - (bug 2059400) as well as increasing the number of pages available (bug - 2063112). + [ Impact ] + The autopkgtest for openvswitch on arm64 currently always fails, which prevents us from catching any real architecture specific regressions as dependencies are updated in the stable release. + + [ Test Plan ] + Trigger autopkgtest runs against PPA and document their output / result. + + [ Regression Potential ] + As this is a test-only change, I'd say none for the actual end user consumption of the package. + + For CI stability however, the issue appears to have been present + throughout the development phase of Noble, so there may be test cases + with architecture specific flakiness which has yet to be uncovered. + Rest assured, we will follow up with any required updates if they do + appear. + + [ Other Info ] + There is an issue with running the DPDK tests on arm64 which is currently worked around by using 1G hugepages as opposed to 2M hugepages (bug 2059400) as well as increasing the number of pages available (bug 2063112). This workaround does however not work for the following tests: - OVS-DPDK - MTU increase vport port - OVS-DPDK - MTU decrease vport port - OVS-DPDK - MTU upper bound vport port - OVS-DPDK - user configured mempool + OVS-DPDK - MTU increase vport port + OVS-DPDK - MTU decrease vport port + OVS-DPDK - MTU upper bound vport port + OVS-DPDK - user configured mempool I propose we skip the test until we find a more permanent solution to this issue. ** Also affects: openvswitch (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063152 Title: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063152] Re: [arm64] autopkgtest - 'OVS-DPDK - MTU increase vport port' test does not fit within CI memory constraints
** Description changed: There is an issue with running the DPDK tests on arm64 which is currently worked around by using 1G hugepages as opposed to 2M hugepages (bug 2059400) as well as increasing the number of pages available (bug 2063112). - This workaround does however not work for the test mentioned in this - bugs summary. + This workaround does however not work for the following tests: + + OVS-DPDK - MTU increase vport port + OVS-DPDK - MTU decrease vport port + OVS-DPDK - MTU upper bound vport port + OVS-DPDK - user configured mempool I propose we skip the test until we find a more permanent solution to this issue. ** Summary changed: - [arm64] autopkgtest - 'OVS-DPDK - MTU increase vport port' test does not fit within CI memory constraints + [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063152 Title: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063112] Re: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed
** Description changed: In bug 2059400 we switch to using 1G hugepages on arm64, as 2M hugepages - does not work. For the OVN autopkgtests using 2 1G hugepages is + does not work. For the OVN autopkgtests using 1 1G hugepage is sufficient, but for the openvswitch autopkgtests that is not enough for all tests to succeed. Bump number of 1G hugepages for the openvswitch autopkgtest. ** Description changed: In bug 2059400 we switch to using 1G hugepages on arm64, as 2M hugepages - does not work. For the OVN autopkgtests using 1 1G hugepage is - sufficient, but for the openvswitch autopkgtests that is not enough for - all tests to succeed. + does not work. For the OVN autopkgtests using 1 1G hugepage per NUNMA + node is sufficient, but for the openvswitch autopkgtests that is not + enough for all tests to succeed. Bump number of 1G hugepages for the openvswitch autopkgtest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063112 Title: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063152] Re: [arm64] autopkgtest - 'OVS-DPDK - MTU increase vport port' test does not fit within CI memory constraints
** Description changed: There is an issue with running the DPDK tests on arm64 which is currently worked around by using 1G hugepages as opposed to 2M hugepages (bug 2059400) as well as increasing the number of pages available (bug 2063112). - This workaround does however not work for the test mention in this bugs - summary. + This workaround does however not work for the test mentioned in this + bugs summary. I propose we skip the test until we find a more permanent solution to this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063152 Title: [arm64] autopkgtest - 'OVS-DPDK - MTU increase vport port' test does not fit within CI memory constraints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063152] [NEW] [arm64] autopkgtest - 'OVS-DPDK - MTU increase vport port' test does not fit within CI memory constraints
Public bug reported: There is an issue with running the DPDK tests on arm64 which is currently worked around by using 1G hugepages as opposed to 2M hugepages (bug 2059400) as well as increasing the number of pages available (bug 2063112). This workaround does however not work for the test mention in this bugs summary. I propose we skip the test until we find a more permanent solution to this issue. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063152 Title: [arm64] autopkgtest - 'OVS-DPDK - MTU increase vport port' test does not fit within CI memory constraints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063112] Re: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed
** Description changed: In bug 2059400 we switch to using 1G hugepages on arm64, as 2M hugepages does not work. For the OVN autopkgtests using 2 1G hugepages is sufficient, but for the openvswitch autopkgtests that is not enough for all tests to succeed. - Bump number of 1G hugepages to 3 for the openvswitch autopkgtest. + Bump number of 1G hugepages for the openvswitch autopkgtest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063112 Title: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063083] Re: flaky autopkgtest - conntrack - zones from other field, more tests
** Description changed: This test appears to be flaky. - https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/oopenvswitch/20240404_222028_2e576@/log.gz - https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/oopenvswitch/20240419_005300_a2bf3@/log.gz + https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/o/openvswitch/20240419_141116_3b7b4@/log.gz + https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/o/openvswitch/20240419_005300_a2bf3@/log.gz + https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/o/openvswitch/20240404_222028_2e576@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/o/openvswitch/20240415_230815_a760a@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063083 Title: flaky autopkgtest - conntrack - zones from other field, more tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063112] [NEW] [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed
Public bug reported: In bug 2059400 we switch to using 1G hugepages on arm64, as 2M hugepages does not work. For the OVN autopkgtests using 2 1G hugepages is sufficient, but for the openvswitch autopkgtests that is not enough for all tests to succeed. Bump number of 1G hugepages to 3 for the openvswitch autopkgtest. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063112 Title: [arm64] autopkgtest - insufficient number of hugepages for all tests to succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062506] Re: autopkgtest - offloads conntrack - ICMP related with SNAT flaky
** Description changed: When run with the CPU/RAM constraints in the autopkgtest cloud, this test currently fails more often than not [0]. Curiously if we switch to using the NMAP netcat implementation the test passes more often than not. An overnight experience provides these statistics: nmap-netcat 57/62 PASS openbsd-netcat 3/62 PASS The upstream developers appear to be using the NMAP netcat implementation more often than the OpenBSD netcat implementation, and for the OVN package the NMAP implementation is required [1]. The curious thing is that when the test is ran with more available resources it passes, so it may also be we are near some resource limit and a that this change alleviates the situation somewhat randomly. However, the fact that upstream develop the tests using the NMAP netcat implementation does shift the scale towards using that implementation in our test runs. Regardless of which netcat implementation used the test does however also remain flaky when colocated with noisy neighbors, so we may want to - also disable the test until its implementation can be improved. + also disable the test until its implementation can be improved. [2-7][8] 0: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240415_172419_494f2@/log.gz 1: https://github.com/ovn-org/ovn/blob/1c9656714c601b128ca0a6bed47050c77e98fb8b/utilities/containers/ubuntu/Dockerfile#L33 + 2: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240421_171007_d187f@/log.gz + 3: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240421_171007_d187f@/log.gz + 4: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240418_195251_f98a6@/log.gz + 5: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240418_195251_f98a6@/log.gz + 6: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240418_194948_321d1@/log.gz + 7: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240418_194948_321d1@/log.gz + 8: https://autopkgtest.ubuntu.com/packages/openvswitch/noble/amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062506 Title: autopkgtest - offloads conntrack - ICMP related with SNAT flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2062506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063083] [NEW] flaky autopkgtest - conntrack - zones from other field, more tests
Public bug reported: This test appears to be flaky. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/oopenvswitch/20240404_222028_2e576@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/oopenvswitch/20240419_005300_a2bf3@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/o/openvswitch/20240415_230815_a760a@/log.gz ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063083 Title: flaky autopkgtest - conntrack - zones from other field, more tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062506] Re: autopkgtest - offloads conntrack - ICMP related with SNAT flaky
** Summary changed: - autopkgtest - offloads conntrack - ICMP related with SNAT fails with openbsd-netcat + autopkgtest - offloads conntrack - ICMP related with SNAT flaky -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062506 Title: autopkgtest - offloads conntrack - ICMP related with SNAT flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2062506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062506] Re: autopkgtest - offloads conntrack - ICMP related with SNAT fails with openbsd-netcat
** Description changed: When run with the CPU/RAM constraints in the autopkgtest cloud, this test currently fails more often than not [0]. Curiously if we switch to using the NMAP netcat implementation the test passes more often than not. An overnight experience provides these statistics: nmap-netcat 57/62 PASS openbsd-netcat 3/62 PASS The upstream developers appear to be using the NMAP netcat implementation more often than the OpenBSD netcat implementation, and for the OVN package the NMAP implementation is required [1]. The curious thing is that when the test is ran with more available resources it passes, so it may also be we are near some resource limit and a that this change alleviates the situation somewhat randomly. However, the fact that upstream develop the tests using the NMAP netcat implementation does shift the scale towards using that implementation in our test runs. + Regardless of which netcat implementation used the test does however + also remain flaky when colocated with noisy neighbors, so we may want to + also disable the test until its implementation can be improved. + 0: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240415_172419_494f2@/log.gz 1: https://github.com/ovn-org/ovn/blob/1c9656714c601b128ca0a6bed47050c77e98fb8b/utilities/containers/ubuntu/Dockerfile#L33 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062506 Title: autopkgtest - offloads conntrack - ICMP related with SNAT fails with openbsd-netcat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2062506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062506] [NEW] autopkgtest - offloads conntrack - ICMP related with SNAT fails with openbsd-netcat
Public bug reported: When run with the CPU/RAM constraints in the autopkgtest cloud, this test currently fails more often than not [0]. Curiously if we switch to using the NMAP netcat implementation the test passes more often than not. An overnight experience provides these statistics: nmap-netcat 57/62 PASS openbsd-netcat 3/62 PASS The upstream developers appear to be using the NMAP netcat implementation more often than the OpenBSD netcat implementation, and for the OVN package the NMAP implementation is required [1]. The curious thing is that when the test is ran with more available resources it passes, so it may also be we are near some resource limit and a that this change alleviates the situation somewhat randomly. However, the fact that upstream develop the tests using the NMAP netcat implementation does shift the scale towards using that implementation in our test runs. 0: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240415_172419_494f2@/log.gz 1: https://github.com/ovn-org/ovn/blob/1c9656714c601b128ca0a6bed47050c77e98fb8b/utilities/containers/ubuntu/Dockerfile#L33 ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062506 Title: autopkgtest - offloads conntrack - ICMP related with SNAT fails with openbsd-netcat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2062506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060941] Re: [ovn 22.03][arm64] ovn -- CoPP test fails
This appears to address the issue: https://github.com/ovn-org/ovn/commit/b0f9a4f48d21f3137457c2e6ae8b1b8a1f367fe9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060941 Title: [ovn 22.03][arm64] ovn -- CoPP test fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2060941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060941] Re: [ovn 22.03][arm64] ovn -- CoPP test fails
** Description changed: - The test configures a meter 10pps meter, then rapidly transmits 40 - packets with Scapy, and checks that a specific amount of drops is sent, - 10. + The test configures a 10pps meter, then rapidly transmits 40 packets + with Scapy, and checks that a specific amount of drops is sent, 10. For some reason the test fails on arm64 because unexpectedly(?) 11 drops are sent instead of 10. Instrumenting the test to capture all packets it looks like this: - # cat all.pcap + # cat all.pcap 09:57:35.324409 ARP, Request who-has 192.168.1.1 tell 192.168.1.2, length 28 09:57:35.324809 ARP, Reply 192.168.1.1 is-at 00:00:01:01:02:03, length 28 09:57:35.354555 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.355898 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.358587 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.359862 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.362505 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.363775 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.367325 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.368595 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.371282 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.372550 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.375247 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.376516 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.379207 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.380474 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.383164 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.384432 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.387191 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.388459 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.391114 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.392383 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.395124 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.399119 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.403109 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.407644 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.411584 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.415491 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.419399 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.423289 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.427181 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.431068 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.434968 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.438849 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.442732 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.446767 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.451360 IP
[Bug 2059097] Re: [SRU] ovn 22.03.7 point release
Yes, unfortunately there appears to be an issue with one of the tests on arm64 which I did not catch prior to the upload ref bug 2060941, so I'm going to request the currently uploaded package to be rejected so that I can upload a new one skipping the faulty test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059097 Title: [SRU] ovn 22.03.7 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2059097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060941] [NEW] [ovn 22.03][arm64] ovn -- CoPP test fails
Public bug reported: The test configures a meter 10pps meter, then rapidly transmits 40 packets with Scapy, and checks that a specific amount of drops is sent, 10. For some reason the test fails on arm64 because unexpectedly(?) 11 drops are sent instead of 10. Instrumenting the test to capture all packets it looks like this: # cat all.pcap 09:57:35.324409 ARP, Request who-has 192.168.1.1 tell 192.168.1.2, length 28 09:57:35.324809 ARP, Reply 192.168.1.1 is-at 00:00:01:01:02:03, length 28 09:57:35.354555 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.355898 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.358587 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.359862 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.362505 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.363775 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.367325 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.368595 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.371282 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.372550 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.375247 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.376516 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.379207 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.380474 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.383164 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.384432 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.387191 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.388459 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.391114 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.392383 IP 192.168.1.1 > 192.168.1.2: ICMP 192.168.1.1 udp port 12345 unreachable, length 100 09:57:35.395124 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.399119 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.403109 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.407644 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.411584 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.415491 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.419399 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.423289 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.427181 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.431068 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.434968 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.438849 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.442732 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.446767 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.451360 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain] 09:57:35.455259 IP 192.168.1.2.53 > 192.168.1.1.12345: 22616 updateDA% [b2&3=0x5858] [22616a] [22616q] [22616n] [22616au] [|domain]
[Bug 2060245] Re: [s390x] proposed migration util-linux 2.39.3-9ubuntu4 vs openvswitch/3.3.0-1build1
** Changed in: openvswitch (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060245 Title: [s390x] proposed migration util-linux 2.39.3-9ubuntu4 vs openvswitch/3.3.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] Re: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11
Upstream fix merged to all branches back to 2.17: https://mail.openvswitch.org/pipermail/ovs-dev/2024-April/413137.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060656] Re: [FFE] Add support for multiple gateway management + BFD/ECMP
** Description changed:
The 2024.1 Caracal release of Neutron (already in archive) includes
features to enable multiple gateway management + associated BFD and ECMP
monitoring and multipathing for external networking in OpenStack.
The command line tooling for this was committed after the 6.6.0 release
of the openstackclient project; in order to expose this features to
OpenStack users on Noble we should pull in the four patches require to
add the sub commands and configuration options for networking.
Neutron feature details:
bug 2002687
Merge detailing patches:
https://code.launchpad.net/~fnordahl/ubuntu/+source/python-
openstackclient/+git/python-openstackclient/+merge/463871
Build logs:
https://launchpad.net/~fnordahl/+archive/ubuntu/dev/+build/28041314
Testing confirmation:
- TBC - Frode to confirm
+ Using the package from the above build test:
+ $ dpkg -l | grep python3-openst
+ ii python3-openstackclient 6.6.0-0ubuntu1.0
all OpenStack Command-line Client - Python 3.x
+
+ I can successfully run the following script that makes use of the
functionality:
+ ROUTER=router10
+ openstack router create \
+ $ROUTER \
+ --disable-snat \
+ --external-gateway net1 \
+ --fixed-ip subnet=subnet1,ip-address=10.50.111.100 \
+ --external-gateway net1 \
+ --fixed-ip subnet=subnet1,ip-address=10.50.111.101 \
+ --external-gateway net2 \
+ --fixed-ip subnet=subnet2,ip-address=10.170.175.100 \
+ --external-gateway net2 \
+ --fixed-ip subnet=subnet2,ip-address=10.170.175.101 \
+ --external-gateway net3 \
+ --fixed-ip subnet=subnet3,ip-address=10.199.89.100 \
+ --external-gateway net3 \
+ --fixed-ip subnet=subnet3,ip-address=10.199.89.101 \
+ --enable-default-route-bfd \
+ --enable-default-route-ecmp
+
+
+---+--+
+ | Field | Value
|
+
+---+--+
+ | admin_state_up| UP
|
+ | availability_zone_hints |
|
+ | availability_zones|
|
+ | created_at| 2024-04-09T10:16:41Z
|
+ | description |
|
+ | distributed | False
|
+ | enable_default_route_bfd | True
|
+ | enable_default_route_ecmp | True
|
+ | enable_ndp_proxy | None
|
+ | external_gateway_info | {"network_id":
"45af3624-43b5-4964-a21f-c3c8f191ca94", "external_fixed_ips": [{"subnet_id":
"61d3485e-26a6-4b08-88fd-d8e7e8e05696", |
+ | | "ip_address": "10.50.111.100"}], "enable_snat":
false}
|
+ | external_gateways | [{'network_id':
'45af3624-43b5-4964-a21f-c3c8f191ca94', 'external_fixed_ips': [{'ip_address':
'10.50.111.100', 'subnet_id': |
+ | | '61d3485e-26a6-4b08-88fd-d8e7e8e05696'}]},
{'network_id': 'ed2466fb-4058-41a3-a3bd-2cbe704b9e1c', 'external_fixed_ips':
[{'ip_address': |
+ | | '10.199.89.101', 'subnet_id':
'8752e2d0-0d6e-45b0-bd24-2fdbbe3f82cc'}]}, {'network_id':
'bab19e53-354c-40c7-948b-1ab2fd54ba00', |
+ | | 'external_fixed_ips': [{'ip_address':
'10.170.175.100', 'subnet_id': '333db8eb-828c-4703-acf6-2a8e56957603'}]},
{'network_id': |
+ |
[Bug 2060245] Re: [s390x] proposed migration util-linux 2.39.3-9ubuntu4 vs openvswitch/3.3.0-1build1
** Changed in: openvswitch (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060245 Title: [s390x] proposed migration util-linux 2.39.3-9ubuntu4 vs openvswitch/3.3.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059400] Re: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
** Changed in: openvswitch (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059400 Title: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2059400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] Re: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11
** Changed in: openvswitch (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] Re: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11
The relevant upstream Python changes are [0][1]. 0: https://github.com/python/cpython/pull/105935 1: https://github.com/python/cpython/issues/116034 ** Bug watch added: github.com/python/cpython/issues #116034 https://github.com/python/cpython/issues/116034 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] Re: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11
** Summary changed: - [noble] FTBFS on failure in test vlog - Python3, change of behavior between Python 3.11 and 3.12 + [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble] FTBFS on failure in test vlog - Python3, change of behavior in Python 3.13, backported to 3.12 and 3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] Re: [noble] FTBFS on failure in test vlog - Python3, change of behavior between Python 3.11 and 3.12
Fix is build testing here: https://launchpad.net/~fnordahl/+archive/ubuntu/ovn- dev/+sourcepub/15919727/+listing-archive-extra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble] FTBFS on failure in test vlog - Python3, change of behavior between Python 3.11 and 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] Re: [noble] FTBFS due to failure in test vlog - Python3
This boils down to a change in behavior for Python 3.12: Consider the script a.py: f = False assert f $ python3 --version Python 3.11.6 $ python3 a.py Traceback (most recent call last): File "/home/ubuntu/a.py", line 2, in assert f AssertionError $ python3 --version Python 3.12.2 $ python3 a.py Traceback (most recent call last): File "/home/frode/tmp/a.py", line 2, in assert f ^ AssertionError ** Summary changed: - [noble][arm64] FTBFS due to failure in test vlog - Python3 + [noble] FTBFS due to failure in test vlog - Python3 ** Summary changed: - [noble] FTBFS due to failure in test vlog - Python3 + [noble] FTBFS on failure in test vlog - Python3, change of behavior between Python 3.11 and 3.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble] FTBFS on failure in test vlog - Python3, change of behavior between Python 3.11 and 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059400] Re: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
** Changed in: openvswitch (Ubuntu) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: openvswitch (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059400 Title: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2059400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] Re: [noble][arm64] FTBFS due to failure in test vlog - Python3
** Changed in: openvswitch (Ubuntu) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: openvswitch (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble][arm64] FTBFS due to failure in test vlog - Python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060434] [NEW] [noble][arm64] FTBFS due to failure in test vlog - Python3
Public bug reported: Full log: https://launchpadlibrarian.net/723457197/buildlog_ubuntu- noble-arm64.openvswitch_3.3.0-1build2_BUILDING.txt.gz ERROR: 1 test was run, 1 failed unexpectedly. ## ## ## Summary of the failures. ## ## ## Failed tests: openvswitch 3.3.0 test suite test groups: NUM: FILE-NAME:LINE TEST-GROUP-NAME KEYWORDS 2531: vlog.at:3 vlog - Python3 ## -- ## ## Detailed failed tests. ## ## -- ## # -*- compilation -*- 2531. vlog.at:3: testing vlog - Python3 ... ../../tests/vlog.at:6: $PYTHON3 $srcdir/test-vlog.py --log-file log_file \ -v dbg module_1:info module_2:warn syslog:off 2>stderr_log ../../tests/vlog.at:9: sed -e 's/.*-.*-.*T..:..:..Z |//' \ -e 's/File ".*", line [0-9][0-9]*,/File , line ,/' \ stderr_log --- - 2024-04-06 13:05:02.236874405 + +++ /<>/_debian/tests/testsuite.dir/at-groups/2531/stdout 2024-04-06 13:05:02.210940554 + @@ -7,31 +7,37 @@ Traceback (most recent call last): File , line , in main assert fail + AssertionError 6 | module_0 | ERR | error exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 7 | module_0 | WARN | warn exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 8 | module_0 | INFO | information exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 9 | module_0 | DBG | debug exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 10 | module_0 | ERR | exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 11 | module_1 | EMER | emergency 12 | module_1 | ERR | error @@ -41,26 +47,31 @@ Traceback (most recent call last): File , line , in main assert fail + AssertionError 17 | module_1 | ERR | error exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 18 | module_1 | WARN | warn exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 19 | module_1 | INFO | information exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 21 | module_1 | ERR | exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 22 | module_2 | EMER | emergency 23 | module_2 | ERR | error @@ -69,20 +80,24 @@ Traceback (most recent call last): File , line , in main assert fail + AssertionError 28 | module_2 | ERR | error exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 29 | module_2 | WARN | warn exception Traceback (most recent call last): File , line , in main assert fail + AssertionError 32 | module_2 | ERR | exception Traceback (most recent call last): File , line , in main assert fail + AssertionError ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060434 Title: [noble][arm64] FTBFS due to failure in test vlog - Python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2060434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059400] Re: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
** Also affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059400 Title: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2059400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059400] Re: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
** Changed in: ovn (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059400 Title: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2059400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059087] Re: [SRU] ovn 23.09.3 point release
Test results for the backport of the noble autopkgtests can be viewed at the following URLs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-fnordahl-sru/mantic/amd64/o/ovn/20240328_132537_1955a@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-fnordahl-sru/mantic/arm64/o/ovn/20240328_134510_6213a@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-fnordahl-sru/mantic/ppc64el/o/ovn/20240328_140007_62f4c@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-fnordahl-sru/mantic/s390x/o/ovn/20240328_124542_f1e11@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059087 Title: [SRU] ovn 23.09.3 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2059087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059400] [NEW] autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
Public bug reported: There appears to be two sets of arm64 nodes used for autopkgtests, the ones coming from the bos02 region are missing a CPU feature that prevents the test from running, the ones coming from the bos03 region have the required CPU features but the test fails [0]. Changing from using 2M hugepages to 1G hugepages resolves the issue. We still need to allocate some 2M hugepages though, to avoid the tests from being skipped. 0: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/o/ovn/20240315_134251_66559@/log.gz ** Affects: ovn (Ubuntu) Importance: Undecided Status: New ** Description changed: There appears to be two sets of arm64 nodes used for autopkgtests, the ones coming from the bos02 region are missing a CPU feature that prevents the test from running, the ones coming from the bos03 region have the required CPU features but the test fails [0]. - Changing from using 2M hugepages to 1G hugepages appear to resolve the - issue. + Changing from using 2M hugepages to 1G hugepages resolves the issue. 0: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/o/ovn/20240315_134251_66559@/log.gz ** Description changed: There appears to be two sets of arm64 nodes used for autopkgtests, the ones coming from the bos02 region are missing a CPU feature that prevents the test from running, the ones coming from the bos03 region have the required CPU features but the test fails [0]. Changing from using 2M hugepages to 1G hugepages resolves the issue. + We still need to allocate some 2M hugepages though, to avoid the tests + from being skipped. + 0: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/o/ovn/20240315_134251_66559@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059400 Title: autopkgtest fails on arm64: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2059400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059097] Re: [SRU] ovn 22.03.7 point release
** Changed in: cloud-archive Status: New => Invalid ** Also affects: cloud-archive/ovn-22.03 Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059097 Title: [SRU] ovn 22.03.7 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2059097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059097] [NEW] [SRU] ovn 22.03.7 point release
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. The update contains the following package updates: * ovn 22.03.7 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. ** Affects: cloud-archive Importance: Undecided Status: Invalid ** Affects: cloud-archive/ovn-22.03 Importance: Undecided Status: New ** Affects: cloud-archive/yoga Importance: Undecided Status: New ** Affects: ovn (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ovn (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu) Status: New => Invalid ** Also affects: ovn (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/yoga Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059097 Title: [SRU] ovn 22.03.7 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2059097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059087] [NEW] [SRU] ovn 23.09.3 point release
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. The update contains the following package updates: * ovn 23.09.3 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. ** Affects: cloud-archive Importance: Undecided Status: New ** Affects: cloud-archive/bobcat Importance: Undecided Status: New ** Affects: ovn (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ovn (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu) Status: New => Invalid ** Also affects: ovn (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/bobcat Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059087 Title: [SRU] ovn 23.09.3 point release To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2059087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
ubuntu@j-lp-2056769:~$ sudo apt install ovn-central ovn-host ubuntu@j-lp-2056769:~$ dpkg -l | grep ovn ii ovn-central 22.03.3-0ubuntu0.22.04.2 amd64OVN central components ii ovn-common 22.03.3-0ubuntu0.22.04.2 amd64OVN common components ii ovn-host22.03.3-0ubuntu0.22.04.2 amd64OVN host components ubuntu@j-lp-2056769:~$ for f in $(dpkg -L ovn-central ovn-common ovn-host | awk '/man.*..gz/') ; do mkdir -p 22.03.3-0ubuntu0.22.04.2;cp $f 22.03.3-0ubuntu0.22.04.2;done ubuntu@j-lp-2056769:~$ sudo apt install ovn-central ovn-host ubuntu@j-lp-2056769:~$ dpkg -l |grep ovn ii ovn-central 22.03.3-0ubuntu0.22.04.3 amd64OVN central components ii ovn-common 22.03.3-0ubuntu0.22.04.3 amd64OVN common components ii ovn-host22.03.3-0ubuntu0.22.04.3 amd64OVN host components ubuntu@j-lp-2056769:~$ for f in $(dpkg -L ovn-central ovn-common ovn-host | awk '/man.*..gz/') ; do mkdir -p 22.03.3-0ubuntu0.22.04.3;cp $f 22.03.3-0ubuntu0.22.04.3;done ubuntu@j-lp-2056769:~/22.03.3-0ubuntu0.22.04.2$ gunzip * ubuntu@j-lp-2056769:~/22.03.3-0ubuntu0.22.04.2$ ls -l total 11 -rw-r--r-- 1 ubuntu ubuntu 8726 Mar 15 09:57 ovn-appctl.8 -rw-r--r-- 1 ubuntu ubuntu 114771 Mar 15 09:57 ovn-architecture.7 -rw-r--r-- 1 ubuntu ubuntu 34283 Mar 15 09:57 ovn-controller.8 -rw-r--r-- 1 ubuntu ubuntu 13301 Mar 15 09:57 ovn-ctl.8 -rw-r--r-- 1 ubuntu ubuntu 6229 Mar 15 09:57 ovn-detrace.1 -rw-r--r-- 1 ubuntu ubuntu 179018 Mar 15 09:57 ovn-nb.5 -rw-r--r-- 1 ubuntu ubuntu 80745 Mar 15 09:57 ovn-nbctl.8 -rw-r--r-- 1 ubuntu ubuntu 162975 Mar 15 09:57 ovn-northd.8 -rw-r--r-- 1 ubuntu ubuntu 171108 Mar 15 09:57 ovn-sb.5 -rw-r--r-- 1 ubuntu ubuntu 46296 Mar 15 09:57 ovn-sbctl.8 -rw-r--r-- 1 ubuntu ubuntu 28886 Mar 15 09:57 ovn-trace.8 ubuntu@j-lp-2056769:~/22.03.3-0ubuntu0.22.04.3$ gunzip * ubuntu@j-lp-2056769:~/22.03.3-0ubuntu0.22.04.3$ ls -l total 11 -rw-r--r-- 1 ubuntu ubuntu 8726 Mar 15 09:57 ovn-appctl.8 -rw-r--r-- 1 ubuntu ubuntu 114771 Mar 15 09:57 ovn-architecture.7 -rw-r--r-- 1 ubuntu ubuntu 34283 Mar 15 09:57 ovn-controller.8 -rw-r--r-- 1 ubuntu ubuntu 13301 Mar 15 09:57 ovn-ctl.8 -rw-r--r-- 1 ubuntu ubuntu 6229 Mar 15 09:57 ovn-detrace.1 -rw-r--r-- 1 ubuntu ubuntu 179018 Mar 15 09:57 ovn-nb.5 -rw-r--r-- 1 ubuntu ubuntu 80745 Mar 15 09:57 ovn-nbctl.8 -rw-r--r-- 1 ubuntu ubuntu 162975 Mar 15 09:57 ovn-northd.8 -rw-r--r-- 1 ubuntu ubuntu 171108 Mar 15 09:57 ovn-sb.5 -rw-r--r-- 1 ubuntu ubuntu 46296 Mar 15 09:57 ovn-sbctl.8 -rw-r--r-- 1 ubuntu ubuntu 28886 Mar 15 09:57 ovn-trace.8 # There is a minor change of contents for the ovn-detrace.1 file which is most likely # caused by the difference in versions of openvswitch-source the two packages are built against. ubuntu@j-lp-2056769:~$ diff -ru 22.03.3-0ubuntu0.22.04.2 22.03.3-0ubuntu0.22.04.3 diff -ru 22.03.3-0ubuntu0.22.04.2/ovn-detrace.1 22.03.3-0ubuntu0.22.04.3/ovn-detrace.1 --- 22.03.3-0ubuntu0.22.04.2/ovn-detrace.1 2024-03-15 09:57:07.523418777 + +++ 22.03.3-0ubuntu0.22.04.3/ovn-detrace.1 2024-03-15 09:57:30.039833756 + @@ -175,7 +175,7 @@ . nr mE \\n(.f . nf . nh -. ft CW +. ft CR .. . . There is no visible difference in how the two versions of the manpage render. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
> You could have versioned the mantic package as 23.09.0-1ubuntu0.2 instead of 23.09.0-1ubuntu1. But since noble is at 24.03.x already, I don't see a conflict arising there. Ack, thanks, I'll make sure to use the expected versioning scheme for SRU's moving forward. > Since this changes how manpages are build, please add a simple test case > check for these. Check that the shipped manpages are built correctly, have no > syntax errors, etc. > Your [Where problems could occur] section is merely stating what you changed, > not what could go wrong. In this particular case, since you are changing how > manpages are built, that is what could go wrong, and is why I ask that you > please add the test case item I mentioned above. Ack, have added a manpage-centric test case and will provide binary package test results in the next comments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
ubuntu@m-lp-2056769:~$ sudo apt install ovn-central ovn-host ubuntu@m-lp-2056769:~$ dpkg -l | grep ovn ii ovn-central 23.09.0-1ubuntu0.1 amd64OVN central components ii ovn-common 23.09.0-1ubuntu0.1 amd64OVN common components ii ovn-host23.09.0-1ubuntu0.1 amd64OVN host components ubuntu@m-lp-2056769:~$ dpkg -L ovn-central ovn-common ovn-host | awk '/man.*..gz/'|xargs zcat|sha1sum 00665fbed247f989d18f5b01ce3404f8ca9b241d - ubuntu@m-lp-2056769:~$ sudo apt -t mantic-proposed install ovn-central ovn-host ubuntu@m-lp-2056769:~$ dpkg -l | grep ovn ii ovn-central 23.09.0-1ubuntu1 amd64OVN central components ii ovn-common 23.09.0-1ubuntu1 amd64OVN common components ii ovn-host23.09.0-1ubuntu1 amd64OVN host components ubuntu@m-lp-2056769:~$ dpkg -L ovn-central ovn-common ovn-host | awk '/man.*..gz/'|xargs zcat|sha1sum 00665fbed247f989d18f5b01ce3404f8ca9b241d - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
** Description changed: [Impact] ovn package currently FTBFS due to changes in the openvswitch package after recent security updates - doc tooling in the openvswitch source package that ovn uses has changed. [Test Case] Build ovn package in mantic or jammy Build fails: make[2]: *** No rule to make target '/home/ubuntu/ovn/b/ovn-22.03.3/ovs/python/build/soutil.py', needed by 'manpages.mk'. Stop. + Confirm manpages are built properly with the new pacakge. + [Where problems could occur] - The proposed patches only change the part of the build process uses to generate documentation (manpages). + The proposed patches change the part of the build process uses to generate documentation (manpages), so we need to make sure the new package actually have manpages properly generated. [Original bug report] make[2]: *** No rule to make target '/home/ubuntu/ovn/b/ovn-22.03.3/ovs/python/build/soutil.py', needed by 'manpages.mk'. Stop. For jammy we need [0]. For mantic we need to drop d/p/revert-ovs-python-build-rename.patch 0: https://github.com/ovn- org/ovn/commit/827ff007a254acb929d06772da42a2bd5c7b2a68 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
This log contains output from the ovn system testsuite for kernel data path with this package source facilitated by backporting the autopkgtest from noble. There is no dpdk data path testsuite available for the version of OVN in jammy. ** Attachment added: "ovn_22.03.3-0ubuntu0.22.04.3-autopkgtest-kmod.log" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+attachment/5756187/+files/ovn_22.03.3-0ubuntu0.22.04.3-autopkgtest-kmod.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
This log contains output from the ovn system testsuite for dpdk data path with this package source facilitated by backporting the autopkgtest from noble. ** Attachment added: "ovn_23.09.0-1ubuntu1-autopkgtest-dpdk.log" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+attachment/5756168/+files/ovn_23.09.0-1ubuntu1-autopkgtest-dpdk.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
This log contains output from the ovn system testsuite for kernel data path with this package source facilitated by backporting the autopkgtest from noble. ** Attachment added: "ovn_23.09.0-1ubuntu1-autopkgtest-kmod.log" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+attachment/5756167/+files/ovn_23.09.0-1ubuntu1-autopkgtest-kmod.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057998] [NEW] autopkgtest fails for binary package test
Public bug reported: When running the autopkgtest using a binary package the test fails with: 342s # Configure OVS before OVN 342s test -d /aZy/ovs || cp -R /usr/src/openvswitch ovs 342s cd ovs && ./configure --enable-ssl --localstatedir=/var --sysconfdir=/etc --prefix=/usr && make -j4 342s /bin/sh: 1: ./configure: not found This happens because the upstream source contains an empty `ovs` directory. We did not see this when preparing the test because when running autopkgtest from package source, the initial build managed by autopkgtest would run `dh clean` which removes the empty `ovs` directory. ** Affects: ovn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057998 Title: autopkgtest fails for binary package test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2057998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057784] [NEW] flaky test: ovn-controller - check sbdb connection
Public bug reported:
As per a recent debian/sid buildlog [0] for the ovn package, the "ovn-
controller - check sbdb connection" appears to be flaky.
0:
https://buildd.debian.org/status/fetch.php?pkg=ovn=amd64=24.03.1-1=1710275203=0
Log excerpt:
# -*- compilation -*-
760. ovn-controller.at:342: testing ovn-controller - check sbdb connection --
parallelization=yes -- ovn_monitor_all=yes ...
creating ovn-sb database
ovsdb-server -vjsonrpc
--remote=punix:/<>/tests/testsuite.dir/760/ovn-sb/ovn-sb.sock
--remote=db:OVN_Southbound,SB_Global,connections
--private-key=/<>/tests/testpki-test-privkey.pem
--certificate=/<>/tests/testpki-test-cert.pem
--ca-cert=/<>/tests/testpki-cacert.pem
/<>/tests/testsuite.dir/760/ovn-sb/ovn-sb.db -vconsole:off
--detach --no-chdir --pidfile --log-file
creating ovn-nb database
ovsdb-server -vjsonrpc
--remote=punix:/<>/tests/testsuite.dir/760/ovn-nb/ovn-nb.sock
/<>/tests/testsuite.dir/760/ovn-nb/ovn-nb.db -vconsole:off
--detach --no-chdir --pidfile --log-file
starting northd
ovn-northd --n-threads=4 -vjsonrpc
--ovnnb-db=unix:/<>/tests/testsuite.dir/760/ovn-nb/ovn-nb.sock
--ovnsb-db=unix:/<>/tests/testsuite.dir/760/ovn-sb/ovn-sb.sock
-vconsole:off --detach --no-chdir --pidfile --log-file
2024-03-12T20:26:33Z|1|ovn_northd|INFO|Using 4 threads
5c883d3f-56fd-4781-a117-8665a3e4a0d8
ovn-macros.at:256: waiting until TCP_PORT=`sed -n 's/.*0:.*: listening on port
\([0-9]*\)$/\1/p' "$d/ovn-sb/ovsdb-server.log"` && test X != X"$TCP_PORT"...
ovn-macros.at:256: wait succeeded immediately
adding simulator 'main'
ovsdb-server
--remote=punix:/<>/tests/testsuite.dir/760/main/db.sock
-vconsole:off --detach --no-chdir --pidfile --log-file
ovs-vswitchd --enable-dummy=system -vvconn -vofproto_dpif -vunixctl
-vconsole:off --detach --no-chdir --pidfile --log-file
adding simulator 'hv'
ovsdb-server --remote=punix:/<>/tests/testsuite.dir/760/hv/db.sock
-vconsole:off --detach --no-chdir --pidfile --log-file
ovs-vswitchd --enable-dummy=system -vvconn -vofproto_dpif -vunixctl
-vconsole:off --detach --no-chdir --pidfile --log-file
ovn-controller --enable-dummy-vif-plug -vconsole:off --detach --no-chdir
--pidfile --log-file
ovs-vsctl: no key "ovn-encap-type-hv" in Open_vSwitch record "." column
external_ids
ovs-vsctl: no key "ovn-encap-ip-hv" in Open_vSwitch record "." column
external_ids
Waiting until ip in sb Encap with chassis_name=hv type=geneve is 192.168.0.1...
ovn-macros.at:584: waiting until
found=$(ovn-${db}ctl --bare --columns $column find $table $a $b $c $d $e)
found=$(for d in $found; do echo $d; done | sort)
test "$expected" = "$found"
...
ovn-macros.at:584: wait succeeded immediately
Waiting until ip in sb Encap with chassis_name=hv type=vxlan is 192.168.0.1...
ovn-macros.at:584: waiting until
found=$(ovn-${db}ctl --bare --columns $column find $table $a $b $c $d $e)
found=$(for d in $found; do echo $d; done | sort)
test "$expected" = "$found"
...
ovn-macros.at:584: wait succeeded immediately
ovn-controller.at:342: waiting until check_sbdb_connection connected...
ovn-controller.at:342: wait succeeded immediately
ovn-controller.at:342: waiting until check_sbdb_connection 'not connected'...
ovn-controller.at:342: wait succeeded immediately
hv: clean up sandbox
./ovn-controller.at:342: test -e $OVS_RUNDIR/ovn-controller.pid
./ovn-controller.at:342: ovs-appctl --timeout=10 -t ovn-controller exit
ovn-controller.at:342: waiting while kill -0 $TMPPID 2>/dev/null...
ovn-controller.at:342: wait succeeded quickly
hv: clean up vswitch
./ovn-controller.at:342: test -e $OVS_RUNDIR/ovs-vswitchd.pid
./ovn-controller.at:342: ovs-appctl --timeout=10 -t ovs-vswitchd exit --cleanup
ovn-controller.at:342: waiting while kill -0 $TMPPID 2>/dev/null...
ovn-controller.at:342: wait succeeded quickly
./ovn-controller.at:342: test -e $OVS_RUNDIR/ovsdb-server.pid
./ovn-controller.at:342: ovs-appctl --timeout=10 -t ovsdb-server exit
ovn-controller.at:342: waiting while kill -0 $TMPPID 2>/dev/null...
ovn-controller.at:342: wait succeeded immediately
./ovn-controller.at:342: check_logs "
$error
/connection failed (No such file or directory)/d
/has no network name*/d
/receive tunnel port not found*/d
/Failed to locate tunnel to reach main chassis/d
" $sbox
--- /dev/null 2024-03-10 22:14:04.0 +
+++ /<>/tests/testsuite.dir/at-groups/760/stdout 2024-03-12
20:26:34.223918134 +
@@ -0,0 +1 @@
+2024-03-12T20:26:33.909Z|00022|stream_tcp|ERR|tcp:192.168.0.10:6642: connect:
Network is unreachable
760. ovn-controller.at:342: 760. ovn-controller - check sbdb connection --
parallelization=yes -- ovn_monitor_all=yes (ovn-controller.at:342): FAILED
(ovn-controller.at:342)
# -*- compilation -*-
761. ovn-controller.at:342: testing ovn-controller - check sbdb connection --
parallelization=yes -- ovn_monitor_all=no ...
creating ovn-sb database
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
** Patch added: "mantic-lp-2056768.debdiff" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+attachment/5754841/+files/mantic-lp-2056768.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
** Patch added: "jammy-lp-2056769.debdiff" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+attachment/5754840/+files/jammy-lp-2056769.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] Re: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
** Description changed: make[2]: *** No rule to make target '/home/ubuntu/ovn/b/ovn-22.03.3/ovs/python/build/soutil.py', needed by 'manpages.mk'. Stop. For jammy we need [0]. - For mantic we need [1] (perhaps partial). + For mantic we need to drop d/p/revert-ovs-python-build-rename.patch - 0: https://github.com/ovn-org/ovn/commit/827ff007a254acb929d06772da42a2bd5c7b2a68 - 1: https://github.com/ovn-org/ovn/commit/558da0cd21ad0172405f7d93c5d0e7533edbf653 + 0: https://github.com/ovn- + org/ovn/commit/827ff007a254acb929d06772da42a2bd5c7b2a68 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056769] [NEW] [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch
Public bug reported: make[2]: *** No rule to make target '/home/ubuntu/ovn/b/ovn-22.03.3/ovs/python/build/soutil.py', needed by 'manpages.mk'. Stop. For jammy we need [0]. For mantic we need [1] (perhaps partial). 0: https://github.com/ovn-org/ovn/commit/827ff007a254acb929d06772da42a2bd5c7b2a68 1: https://github.com/ovn-org/ovn/commit/558da0cd21ad0172405f7d93c5d0e7533edbf653 ** Affects: ovn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056769 Title: [jammy/mantic] ftbfs due to build-time incompatibility with updated openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2056769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055862] [NEW] ovn-vif ci: the CI pipeline fails due to too old scapy
Public bug reported: The upstream OVN VIF CI pipeline currently fails due to a too old version of scapy. This condition is visible in the "dns lookup : EDNS" test and the following hint is provided in the scapy.log: 2024-03-04T07:31:01.779Z | 0 | scapy-server | INFO | scapy server ready 2024-03-04T07:31:01.911Z | 3 | scapy-server | INFO | received payload request: Ether(dst='00:00:00:00:00:02', src='00:00:00:00:00:01') / IP(dst='10.0.0.254', src='10.0.0.1') / UDP(sport=42424, dport=53) /DNS(rd=1, qd=DNSQR(qname='foo.ovn.org'), arcount=1, ar= DNSRR(type='OPT', rclass=4096, rdata=EDNS0ClientSubnet(source_plen=24, address='10.0.0.1'))) 2024-03-04T07:31:01.913Z | 4 | scapy-server | ERR | failed to process payload request: name 'EDNS0ClientSubnet' is not defined Traceback (most recent call last): File "/home/ubuntu/src/ovn-vif/ovn/tests/testsuite.dir/159/../../../tests/scapy-server.py", line 32, in process return binascii.hexlify(raw(eval(data))).decode() File "", line 1, in NameError: name 'EDNS0ClientSubnet' is not defined This test works for the upstream OVN CI because they are running the testsuite inside a container based on the latest Ubuntu version [0]. We need to do something similar for the OVN VIF CI. 0: https://github.com/ovn- org/ovn/blob/main/utilities/containers/ubuntu/Dockerfile ** Affects: ovn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055862 Title: ovn-vif ci: the CI pipeline fails due to too old scapy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2055862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Changed in: ovn (Ubuntu) Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Changed in: ovn (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Also affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Changed in: openvswitch (Ubuntu) Status: New => Triaged ** Changed in: openvswitch (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
A possible fix is being discussed in [7]. 7: https://mail.openvswitch.org/pipermail/ovs-dev/2022-May/393981.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
A update on some findings. If we either revert OVS commit [4], OR change a open vswitch kernel data path function [5] to always return 'false' (credits to Numan), the problem goes away. This also appears to be a root of a different issue previously reported to the ovs-discuss list [6]. 4: https://github.com/openvswitch/ovs/commit/355fef6f2 5: https://elixir.bootlin.com/linux/latest/source/net/openvswitch/conntrack.c#L683 6: https://mail.openvswitch.org/pipermail/ovs-discuss/2022-March/051771.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947127] Re: [SRU] Some DNS extensions not working with OVN
** Also affects: neutron (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: cloud-archive/xena Importance: Undecided Status: New ** Also affects: cloud-archive/yoga Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947127 Title: [SRU] Some DNS extensions not working with OVN To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1947127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972648] [NEW] Schema upgrade unsuccessful at first attempt, succeds at second attempt
Public bug reported: When upgrading the OVN package on the unit that first was used to create a DB cluster (i.e. `--db-Xb-cluster-remote-addr` is empty in /etc/default/ovn-central) the `ovn-ctl` script will perform Schema upgrade of the cluster. This sometimes fails in the first attempt, but succeeds in the second attempt by just restarting the appropriate OVN DB systemd service. This is with only upgrading the package on the lead unit, leaving the other nodes available in the cluster. No trace of the failure is to be found in the logs so we can only guess what is happening. Looking at the CTL library code [0] I suspect that the default of using a 30 second timeout [1] for the entire `ovsdb-client` invocation is insufficient if the system is slow/busy/has large db/need compaction/snapshot etc etc. 0: https://github.com/openvswitch/ovs/blob/9dd3031d2e0e9597449e95428320ccaaff7d8b3d/utilities/ovs-lib.in#L490 1: https://github.com/openvswitch/ovs/blob/9dd3031d2e0e9597449e95428320ccaaff7d8b3d/lib/timeval.c#L257-L271 ** Affects: ovn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972648 Title: Schema upgrade unsuccessful at first attempt, succeds at second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1972648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971178] [NEW] [jammy] Missing ovn-detrace binary
Public bug reported: Upstream changes [0] has made `ovn-detrace` into a symbolical link to `ovn_detrace.py`. As a consequence the package now only contains the link and not the actual binary. 0: https://github.com/ovn- org/ovn/commit/1cafb6306df95311d31124bde26bebb2bb76d308 ** Affects: ovn (Ubuntu) Importance: High Status: Triaged ** Changed in: ovn (Ubuntu) Status: New => Triaged ** Changed in: ovn (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971178 Title: [jammy] Missing ovn-detrace binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1971178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
The current line of thought is that the change in OVN has uncovered a conntrack related bug in either OVS, the OVS kernel datapath or kernel CT in general ref [3]. 3: https://mail.openvswitch.org/pipermail/ovs-dev/2022-April/393426.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Patch added: "test-synthesis.patch" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5579267/+files/test-synthesis.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
Updated OVN to main and it unfortunately made no difference. The combination of stateless on the NAT rule and the allow-related ACLs does indeed look strange, but this is how OpenStack sets it up. Have not looked into whether that makes sense or not yet. To ensure we're looking at the same thing I made this modification to the `DNAT LR hairpin IPv4` system test [2] And executed it like this: sudo make check-kernel TESTSUITEFLAGS="337" It fails consistently here. If I either revert [1] or remove the check for the second ping from the test it succeeds. 2: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5579267/+files/test-synthesis.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
Sure thing! In this DB the active gateway chassis is `deep-ferret.maas` and the instance on `comic-perch.maas` is unable to have two ping sessions to itself using non-distributed FIP 10.78.95.196. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Attachment added: "ovnsb_db.db" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5577953/+files/ovnsb_db.db -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Attachment added: "ovnnb_db.db" https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5577952/+files/ovnnb_db.db -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] Re: Hairpin traffic does not work with centralized NAT gw
** Changed in: ovn (Ubuntu) Status: New => Triaged ** Changed in: ovn (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967856] [NEW] Hairpin traffic does not work with centralized NAT gw
Public bug reported: If you have two hvs where hv1 is the gateway chassis and you have an instance running on hv2. On instance on hv2 hairpin traffic works for the first session, but not for the next: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.07 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. --- 10.78.95.89 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7334,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7334,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7335,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7335,type=0,code=0),zone=7 We made an attempt at using OVN built with [0], but that did unfortunately not help. If we however revert [1] it works again: $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=1.31 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 1.318/1.318/1.318/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 $ ping -c1 10.78.95.89 PING 10.78.95.89 (10.78.95.89) 56(84) bytes of data. 64 bytes from 10.78.95.89: icmp_seq=1 ttl=62 time=0.307 ms --- 10.78.95.89 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.307/0.307/0.307/0.000 ms $ sudo ovs-appctl -t ovs-vswitchd dpctl/dump-conntrack icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=0,code=0),zone=1 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7337,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7337,type=0,code=0),zone=7 icmp,orig=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=8,code=0),reply=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=7 icmp,orig=(src=10.78.95.89,dst=192.168.0.211,id=7336,type=8,code=0),reply=(src=192.168.0.211,dst=10.78.95.89,id=7336,type=0,code=0),zone=1 0: https://patchwork.ozlabs.org/project/ovn/patch/20220401175516.2139179-1-mmich...@redhat.com/ 1: https://github.com/ovn-org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a ** Affects: ovn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967856 Title: Hairpin traffic does not work with centralized NAT gw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967718] [NEW] Traffic sent to LRP port recirculate until TTL=0
Public bug reported: When TCP/UDP traffic is sent to the address of an LRP port and at the same time is not part of any SNAT/DNAT conversation, it will keep recirculating in the OVS data plane until TTL is 0. When the packet eventually drops, you might get this message logged: [ 58.586597] openvswitch: ovs-system: deferred action limit reached, drop recirc action This behavior is problematic because it wastes resources and could also trigger other potential problems in the data plane quite quickly [0]. For any internet connected system it is also highly likely to occur. As mentioned above the LRP address is used for both SNAT return traffic and DNAT forwarding, so we would need to allow that traffic to pass and at the same time install flows to prevent this from happening. 0: https://mail.openvswitch.org/pipermail/ovs- discuss/2022-March/051780.html ** Affects: ovn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967718 Title: Traffic sent to LRP port recirculate until TTL=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966981] Re: [hwol] centralized gateway NAT mangles source address
** Description changed: When hardware offload is enabled, CMS configures gateway routers and centralized NAT, the source address of packets flowing through the gateway are mangled after the connection preamble, not allowing the connection to form. Return traffic on connections established from the instance are also affected, even for UDP (DNS). Example outside-in TCP connection attempt: tcpdump: listening on tape5c1862d-b4, link-type EN10MB (Ethernet), capture size 262144 bytes 05:52:04.286472 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 62, id 8865, offset 0, flags [DF], proto TCP (6), length 60) 10.11.2.11.57704 > 10.42.3.34.22: Flags [S], cksum 0x1e2a (correct), seq 3991821787, win 64240, options [mss 1460,sackOK,TS val 943370240 ecr 0,nop,wscale 7], length 0 05:52:04.286661 fa:16:3e:fc:82:be > fa:16:3e:c8:19:af, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) 10.42.3.34.22 > 10.11.2.11.57704: Flags [S.], cksum 0x1990 (incorrect -> 0xdac4), seq 2903091535, ack 3991821788, win 62230, options [mss 8902,sackOK,TS val 2422032229 ecr 943370240,nop,wscale 7], length 0 05:52:04.287314 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 62, id 8866, offset 0, flags [DF], proto TCP (6), length 52) 10.11.2.11.57704 > 10.42.3.34.22: Flags [.], cksum 0x17c3 (correct), seq 1, ack 1, win 502, options [nop,nop,TS val 943370241 ecr 2422032229], length 0 05:52:04.287589 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 107: (tos 0x0, ttl 62, id 8867, offset 0, flags [DF], proto TCP (6), length 93) 0.0.0.0.57704 > 10.42.3.34.22: Flags [P.], cksum 0x017f (correct), seq 3991821788:3991821829, ack 2903091536, win 502, options [nop,nop,TS val 943370242 ecr 2422032229], length 41 Return traffic on connection-less UDP streams are also affected: 05:51:56.441418 fa:16:3e:fc:82:be > fa:16:3e:c8:19:af, ethertype IPv4 (0x0800), length 104: (tos 0x0, ttl 64, id 56915, offset 0, flags [DF], proto UDP (17), length 90) 10.42.3.34.57502 > 194.169.254.1.53: [bad udp cksum 0xce4e -> 0x88d1!] 38125+ ? fnordahl-bastion.openstack.partnercloud1.lan. (62) 05:51:56.443387 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 179: (tos 0x0, ttl 63, id 64535, offset 0, flags [DF], proto UDP (17), length 165) 0.0.0.0.53 > 10.42.3.34.57502: [udp sum ok] 38125 NXDomain q: ? fnordahl-bastion.openstack.partnercloud1.lan. 0/1/0 ns: . SOA a.root-servers.net. nstld.verisign-grs.com. 2022033100 1800 900 604800 86400 (137) Enabling distributed floating IP (aka DVR) the problem goes away. When disabling hardware offload completely the problem goes away. Running ovn-northd without [0] also makes the problem go away. + Versions: + OVS 2.17.0 + OVN 22.03.0 + Kernel 5.15.0-23-generic + + Hardware: ConnectX-6 Dx MCX623106AN-CDAT + Firmware: 22.32.2004 + Driver: OFED 5.5-1.0.3.2 + 0: https://github.com/ovn- org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a ** Description changed: When hardware offload is enabled, CMS configures gateway routers and centralized NAT, the source address of packets flowing through the gateway are mangled after the connection preamble, not allowing the connection to form. Return traffic on connections established from the instance are also affected, even for UDP (DNS). Example outside-in TCP connection attempt: tcpdump: listening on tape5c1862d-b4, link-type EN10MB (Ethernet), capture size 262144 bytes 05:52:04.286472 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 62, id 8865, offset 0, flags [DF], proto TCP (6), length 60) 10.11.2.11.57704 > 10.42.3.34.22: Flags [S], cksum 0x1e2a (correct), seq 3991821787, win 64240, options [mss 1460,sackOK,TS val 943370240 ecr 0,nop,wscale 7], length 0 05:52:04.286661 fa:16:3e:fc:82:be > fa:16:3e:c8:19:af, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) 10.42.3.34.22 > 10.11.2.11.57704: Flags [S.], cksum 0x1990 (incorrect -> 0xdac4), seq 2903091535, ack 3991821788, win 62230, options [mss 8902,sackOK,TS val 2422032229 ecr 943370240,nop,wscale 7], length 0 05:52:04.287314 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 62, id 8866, offset 0, flags [DF], proto TCP (6), length 52) 10.11.2.11.57704 > 10.42.3.34.22: Flags [.], cksum 0x17c3 (correct), seq 1, ack 1, win 502, options [nop,nop,TS val 943370241 ecr 2422032229], length 0 05:52:04.287589 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 107: (tos 0x0, ttl 62, id 8867, offset 0, flags [DF], proto TCP (6), length 93) 0.0.0.0.57704 > 10.42.3.34.22: Flags [P.], cksum 0x017f (correct), seq 3991821788:3991821829, ack
[Bug 1966981] Re: [hwol] centralized gateway NAT mangles source address
** Description changed: When hardware offload is enabled, CMS configures gateway routers and centralized NAT, the source address of packets flowing through the gateway are mangled after the connection preamble, not allowing the - connection to form. + connection to form: + + tcpdump: listening on tape5c1862d-b4, link-type EN10MB (Ethernet), capture size 262144 bytes + 05:52:04.286472 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 62, id 8865, offset 0, flags [DF], proto TCP (6), length 60) + 10.11.2.11.57704 > 10.42.3.34.22: Flags [S], cksum 0x1e2a (correct), seq 3991821787, win 64240, options [mss 1460,sackOK,TS val 943370240 ecr 0,nop,wscale 7], length 0 + 05:52:04.286661 fa:16:3e:fc:82:be > fa:16:3e:c8:19:af, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) + 10.42.3.34.22 > 10.11.2.11.57704: Flags [S.], cksum 0x1990 (incorrect -> 0xdac4), seq 2903091535, ack 3991821788, win 62230, options [mss 8902,sackOK,TS val 2422032229 ecr 943370240,nop,wscale 7], length 0 + 05:52:04.287314 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 62, id 8866, offset 0, flags [DF], proto TCP (6), length 52) + 10.11.2.11.57704 > 10.42.3.34.22: Flags [.], cksum 0x17c3 (correct), seq 1, ack 1, win 502, options [nop,nop,TS val 943370241 ecr 2422032229], length 0 + 05:52:04.287589 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 107: (tos 0x0, ttl 62, id 8867, offset 0, flags [DF], proto TCP (6), length 93) + 0.0.0.0.57704 > 10.42.3.34.22: Flags [P.], cksum 0x017f (correct), seq 3991821788:3991821829, ack 2903091536, win 502, options [nop,nop,TS val 943370242 ecr 2422032229], length 41 + When disabling hardware offload completely the problem goes away. Running ovn-northd without [0] also makes the problem go away. 0: https://github.com/ovn- org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a ** Description changed: When hardware offload is enabled, CMS configures gateway routers and centralized NAT, the source address of packets flowing through the gateway are mangled after the connection preamble, not allowing the connection to form: tcpdump: listening on tape5c1862d-b4, link-type EN10MB (Ethernet), capture size 262144 bytes 05:52:04.286472 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 62, id 8865, offset 0, flags [DF], proto TCP (6), length 60) - 10.11.2.11.57704 > 10.42.3.34.22: Flags [S], cksum 0x1e2a (correct), seq 3991821787, win 64240, options [mss 1460,sackOK,TS val 943370240 ecr 0,nop,wscale 7], length 0 + 10.11.2.11.57704 > 10.42.3.34.22: Flags [S], cksum 0x1e2a (correct), seq 3991821787, win 64240, options [mss 1460,sackOK,TS val 943370240 ecr 0,nop,wscale 7], length 0 05:52:04.286661 fa:16:3e:fc:82:be > fa:16:3e:c8:19:af, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) - 10.42.3.34.22 > 10.11.2.11.57704: Flags [S.], cksum 0x1990 (incorrect -> 0xdac4), seq 2903091535, ack 3991821788, win 62230, options [mss 8902,sackOK,TS val 2422032229 ecr 943370240,nop,wscale 7], length 0 + 10.42.3.34.22 > 10.11.2.11.57704: Flags [S.], cksum 0x1990 (incorrect -> 0xdac4), seq 2903091535, ack 3991821788, win 62230, options [mss 8902,sackOK,TS val 2422032229 ecr 943370240,nop,wscale 7], length 0 05:52:04.287314 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 66: (tos 0x0, ttl 62, id 8866, offset 0, flags [DF], proto TCP (6), length 52) - 10.11.2.11.57704 > 10.42.3.34.22: Flags [.], cksum 0x17c3 (correct), seq 1, ack 1, win 502, options [nop,nop,TS val 943370241 ecr 2422032229], length 0 + 10.11.2.11.57704 > 10.42.3.34.22: Flags [.], cksum 0x17c3 (correct), seq 1, ack 1, win 502, options [nop,nop,TS val 943370241 ecr 2422032229], length 0 05:52:04.287589 fa:16:3e:c8:19:af > fa:16:3e:fc:82:be, ethertype IPv4 (0x0800), length 107: (tos 0x0, ttl 62, id 8867, offset 0, flags [DF], proto TCP (6), length 93) - 0.0.0.0.57704 > 10.42.3.34.22: Flags [P.], cksum 0x017f (correct), seq 3991821788:3991821829, ack 2903091536, win 502, options [nop,nop,TS val 943370242 ecr 2422032229], length 41 + 0.0.0.0.57704 > 10.42.3.34.22: Flags [P.], cksum 0x017f (correct), seq 3991821788:3991821829, ack 2903091536, win 502, options [nop,nop,TS val 943370242 ecr 2422032229], length 41 + Enabling distributed floating IP (aka DVR) the problem goes away. When disabling hardware offload completely the problem goes away. Running ovn-northd without [0] also makes the problem go away. 0: https://github.com/ovn- org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a ** Description changed: When hardware offload is enabled, CMS configures gateway routers and centralized NAT, the source address of packets flowing through
[Bug 1966981] Re: [hwol] centralized gateway NAT non-functional
** Summary changed: - Gateway router NAT non-functional for OVN 22.03 + [hwol] centralized gateway NAT non-functional ** Summary changed: - [hwol] centralized gateway NAT non-functional + [hwol] centralized gateway NAT mangles source address ** Description changed: - I currently do not have all the details, but I do know that OVN 21.12 - and 22.03 brings a regression as to how NAT is processed for CMS'es that - make use of gateway routers, such as OpenStack. + When hardware offload is enabled, CMS configures gateway routers and + centralized NAT, the source address of packets flowing through the + gateway are mangled after the connection preamble, not allowing the + connection to form. - We've tracked the regression down to a single commit [0]. + When disabling hardware offload completely the problem goes away. + + Running ovn-northd without [0] also makes the problem go away. 0: https://github.com/ovn- org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a ** Changed in: ovn (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966981 Title: [hwol] centralized gateway NAT mangles source address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1966981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966981] [NEW] Gateway router NAT non-functional for OVN 22.03
Public bug reported: I currently do not have all the details, but I do know that OVN 21.12 and 22.03 brings a regression as to how NAT is processed for CMS'es that make use of gateway routers, such as OpenStack. We've tracked the regression down to a single commit [0]. 0: https://github.com/ovn- org/ovn/commit/4deac4509abbedd6ffaecf27eed01ddefccea40a ** Affects: ovn (Ubuntu) Importance: Critical Status: Triaged ** Changed in: ovn (Ubuntu) Status: New => Triaged ** Changed in: ovn (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966981 Title: Gateway router NAT non-functional for OVN 22.03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1966981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940043] Re: Upgrade from OVN 20.03 to newer OVN version will cause data plane outage
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Fix Released ** Changed in: cloud-archive/wallaby Importance: Undecided => High ** Changed in: cloud-archive/wallaby Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: cloud-archive/wallaby Status: New => Triaged ** Changed in: ovn (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940043 Title: Upgrade from OVN 20.03 to newer OVN version will cause data plane outage To manage notifications about this bug go to: https://bugs.launchpad.net/charm-layer-ovn/+bug/1940043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957817] Re: Multicast traffic is broken between VMs on different hypervisors using provider networks
Control test: With basis in the OVN package currently in the Focal Main archive, I added only the functional test part of debian/patches/lp-1957817-ovn-northd-Add-localnet-ports-to-Multicast_Groups-cr.patch ## --- ## ## ovn 20.03.2 test suite. ## ## --- ## OVN end-to-end tests 117: ovn -- IGMP snoop/querier/relay FAILED (ovs-macros.at:222) 118: ovn -- MLD snoop/querier/relay FAILED (ovs-macros.at:222) ## - ## ## Test results. ## ## - ## ERROR: All 2 tests were run, 2 failed unexpectedly. Now instead download source of the proposed package and build it: ## --- ## ## ovn 20.03.2 test suite. ## ## --- ## ... 117: ovn -- IGMP snoop/querier/relay ok 118: ovn -- MLD snoop/querier/relay ok ... ## - ## ## Test results. ## ## - ## All 242 tests were successful. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957817 Title: Multicast traffic is broken between VMs on different hypervisors using provider networks To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1957817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857026] Re: OVN doesn't seem to support reverse DNS lookups for instances
Deployed focal-wallaby from charm-neutron-api-plugin-ovn gate tests and patched
Neutron for some unresolved issues at Wallaby. The need to do that is
unfortunate but this verificat
ion is about the OVN pacakges, so let's focus on them.
With two instances running we can see the following information in the OVN DB:
$ sudo ovn-nbctl list dns
_uuid : a62d480f-e5ad-421e-9e8a-ab4072232331
external_ids: {ls_name=neutron-7d2d7f7e-ebb9-4625-a2ab-8bb6647f1988}
records :
{"182.0.168.192.in-addr.arpa"=zaza-neutrontests-ins-1.openstack.example,
"239.0.168.192.in-addr.arpa"=zaza-neutrontests-ins-2.openstack.example,
zaza-neutrontests-ins-1="192.168.0.182",
zaza-neutrontests-ins-1.openstack.example="192.168.0.182",
zaza-neutrontests-ins-2="192.168.0.239",
zaza-neutrontests-ins-2.openstack.example="192.168.0.239"}
Control test:
From instance forward DNS lookups of other instance names work:
$ host zaza-neutrontests-ins-1.openstack.example
zaza-neutrontests-ins-1.openstack.example has address 192.168.0.182
But reverse DNS lookup of other instance IP does not work:
$ host 192.168.0.182
Host 182.0.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
Upgrade to packages from -proposed:
$ juju run --application ovn-chassis 'dpkg -l | grep ovn'
- Stdout: |
ii neutron-ovn-metadata-agent2:18.1.1-0ubuntu2~cloud0
all Neutron is a virtual network service for
Openstack - OVN metadata agent
ii ovn-common20.12.0-0ubuntu3.1~cloud0
amd64OVN common components
ii ovn-host 20.12.0-0ubuntu3.1~cloud0
amd64OVN host components
UnitId: ovn-chassis/0
- Stdout: |
ii neutron-ovn-metadata-agent2:18.1.1-0ubuntu2~cloud0
all Neutron is a virtual network service for
Openstack - OVN metadata agent
ii ovn-common20.12.0-0ubuntu3.1~cloud0
amd64OVN common components
ii ovn-host 20.12.0-0ubuntu3.1~cloud0
amd64OVN host components
UnitId: ovn-chassis/1
Confirm updated packages work:
$ sudo systemctl restart systemd-resolved
$ host zaza-neutrontests-ins-1.openstack.example
zaza-neutrontests-ins-1.openstack.example has address 192.168.0.182
$ host 192.168.0.182
182.0.168.192.in-addr.arpa domain name pointer
zaza-neutrontests-ins-1.openstack.example.
** Tags removed: verification-needed verification-wallaby-needed
** Tags added: verification-done verification-wallaby-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857026
Title:
OVN doesn't seem to support reverse DNS lookups for instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-central/+bug/1857026/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857026] Re: OVN doesn't seem to support reverse DNS lookups for instances
Deployed focal-ussuri from charm-neutron-api-plugin-ovn gate tests and
applied pending Neutron patch [0].
With two instances running we can see the following information in the OVN DB:
$ sudo ovn-nbctl list dns
_uuid : d51565b8-4ddb-4038-8a92-55e25247a419
external_ids: {ls_name=neutron-de1d0eb4-405a-4fc1-98ef-b93c7a2a4524}
records :
{"114.0.168.192.in-addr.arpa"=zaza-neutrontests-ins-1.openstack.example,
"13.0.168.192.in-addr.arpa"=zaza-neutrontests-ins-2.openstack.example,
zaza-neutrontests-ins-1="192.168.0.114",
zaza-neutrontests-ins-1.openstack.example="192.168.0.114",
zaza-neutrontests-ins-2="192.168.0.13",
zaza-neutrontests-ins-2.openstack.example="192.168.0.13"}
Control test:
From instance forward DNS lookups of other instance names work:
$ host zaza-neutrontests-ins-1.openstack.example
zaza-neutrontests-ins-1.openstack.example has address 192.168.0.114
But reverse DNS lookup of other instance IP does not work:
$ host 192.168.0.114
Host 114.0.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
Upgrade to packages from -proposed:
$ juju run --application ovn-chassis 'dpkg -l | grep ovn'
- Stdout: |
ii neutron-ovn-metadata-agent2:16.4.2-0ubuntu1
all Neutron is a virtual network service for
Openstack - OVN metadata agent
ii ovn-common20.03.2-0ubuntu0.20.04.3
amd64OVN common components
ii ovn-host 20.03.2-0ubuntu0.20.04.3
amd64OVN host components
UnitId: ovn-chassis/0
- Stdout: |
ii neutron-ovn-metadata-agent2:16.4.2-0ubuntu1
all Neutron is a virtual network service for
Openstack - OVN metadata agent
ii ovn-common20.03.2-0ubuntu0.20.04.3
amd64OVN common components
ii ovn-host 20.03.2-0ubuntu0.20.04.3
amd64OVN host components
UnitId: ovn-chassis/1
Confirm updated packages work:
$ sudo systemctl restart systemd-resolved
$ host zaza-neutrontests-ins-1.openstack.example
zaza-neutrontests-ins-1.openstack.example has address 192.168.0.114
$ host 192.168.0.114
114.0.168.192.in-addr.arpa domain name pointer
zaza-neutrontests-ins-1.openstack.example.
0: curl
https://review.opendev.org/changes/openstack%2Fneutron~823631/revisions/2/patch?download|base64
-d|sudo patch -p2
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857026
Title:
OVN doesn't seem to support reverse DNS lookups for instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-central/+bug/1857026/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964348] Re: [20.03][20.12] ovn-controller should update OF rules atomically
** Changed in: cloud-archive Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964348 Title: [20.03][20.12] ovn-controller should update OF rules atomically To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1964348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964348] [NEW] [20.03][20.12] ovn-controller should update OF rules atomically
Public bug reported: Originally reported at [0] and fixed in OVN 21.06 by [1]. If some OF rules needs to be replaced due to logical flow changes, ovn-controller deletes old rules first and adds new ones later. In a complex scenario with big number of flows a lot of time can pass between these events leading to the dataplane downtime and packet loss. Also, while these changes are in progress, OVS will use incomplete pipelines that will also lead to packet drops. To avoid this, all flow modifications should be done atomically, so there will be always some version of OF rules installed that can handle dataplane traffic and it will be complete in terms of reflecting some consistent set of logical flows. Wrapping all flow modifications into atomic ordered bundle to achieve that. 0: https://bugzilla.redhat.com/1947398 1: https://github.com/ovn-org/ovn/commit/7687d878f1e30c98d52b37bade42293f2a1e9bd3 ** Affects: cloud-archive Importance: Undecided Status: New ** Affects: cloud-archive/wallaby Importance: Undecided Status: New ** Affects: ovn (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu) Status: New => Fix Released ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964348 Title: [20.03][20.12] ovn-controller should update OF rules atomically To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1964348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857026] Re: OVN doesn't seem to support reverse DNS lookups for instances
Description updated with SRU documentation, apologies for the delay. ** Description changed: - There's an upstream bug that mentions this during implementation of - regular DNS lookups - - https://bugzilla.redhat.com/show_bug.cgi?id=1503521 + [Impact] + At Focal we took a stance that moving forward new deployments of Charmed OpenStack should use OVN as the SDN. For clouds upgrading, Focal is also the point for which a migration from ML2/OVS to ML2/OVN should take place before further upgrades are applied. + + The current lack of support for reverse DNS lookup for IP addresses + belonging to project instances would prevent users with applications + depending on this feature to commence new deployments or upgrade through + Focal and beyond. + + [Test Plan] + Deploy a Charmed OpenStack and perform forward and reverse DNS lookups for instance names and addresses with the old and new packages to confirm. + + [Regression Potential] + The instance DNS resolution in OVN works by looking up records in the OVN Southbound database. The CMS adds records for both forward and reverse lookups and the OVN controller needs to know how to look for them. The included patches have been available for several upstream releases without any reported issues. In addition we have been running internal clouds with these patches without issues. + + [Original Bug Description] + There's an upstream bug that mentions this during implementation of regular DNS lookups - https://bugzilla.redhat.com/show_bug.cgi?id=1503521 ** Changed in: ovn (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857026 Title: OVN doesn't seem to support reverse DNS lookups for instances To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1857026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957817] Re: Multicast traffic is broken between VMs on different hypervisors using provider networks
Description updated with SRU documentation, apologies for the delay. ** Description changed: - In an OpenStack Ussuri (both Focal and Bionic) cloud we discovered that - multicast traffic would fail between VMs on different hypervisors and - when using provider networks. The following table reflects what we - found works/didn't work: + [Impact] + In an OpenStack Ussuri (both Focal and Bionic) cloud we discovered that multicast traffic would fail between VMs on different hypervisors and when using provider networks. - https://paste.ubuntu.com/p/QZZBjrTSFQ/ + [Test Plan] + The upstream fix also contains an addition to the OVN testsuite confirming the correct behavior. We cat utilize this test case to perform both a control test on a unmodified package as well as confirming that a updated package fixes the problem. + + [Regression Potential] + The fix touches a code path that is executed only when OVN is configured to enable handling of Multicast traffic. The fix has also been available for several upstream releases without any reported issues. + + [Original Bug Description] + In an OpenStack Ussuri (both Focal and Bionic) cloud we discovered that multicast traffic would fail between VMs on different hypervisors and when using provider networks. The following table reflects what we found works/didn't work: + + https://paste.ubuntu.com/p/QZZBjrTSFQ/ Based on this, I went looking at relevant changes upstream and found that this appears to have been fixed upstream, but not backported to OVN 20.03: https://github.com/ovn- org/ovn/commit/97778ab3e422ac071faa67f9f477fd54977e9c04 I backported this patch to the version of OVN in Ussuri here: https://launchpad.net/~elmo/+archive/ubuntu/sf322809 These patched packages have been tested on a customer site and confirmed to fix the problem. I've attached the patch from the PPA for convenience. ** Changed in: ovn (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957817 Title: Multicast traffic is broken between VMs on different hypervisors using provider networks To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1957817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957817] Re: Multicast traffic is broken between VMs on different hypervisors using provider networks
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957817 Title: Multicast traffic is broken between VMs on different hypervisors using provider networks To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1957817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857026] Re: OVN doesn't seem to support reverse DNS lookups for instances
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/wallaby Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857026 Title: OVN doesn't seem to support reverse DNS lookups for instances To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1857026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857026] Re: OVN doesn't seem to support reverse DNS lookups for instances
** Merge proposal unlinked: https://code.launchpad.net/~fnordahl/ubuntu/+source/ovn/+git/ovn/+merge/416078 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857026 Title: OVN doesn't seem to support reverse DNS lookups for instances To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ovn-central/+bug/1857026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957817] Re: Multicast traffic is broken between VMs on different hypervisors using provider networks
** Also affects: ovn (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ovn (Ubuntu Focal) Status: New => In Progress ** Changed in: ovn (Ubuntu Focal) Importance: Undecided => High ** Changed in: ovn (Ubuntu Focal) Assignee: (unassigned) => Frode Nordahl (fnordahl) ** Changed in: ovn (Ubuntu) Importance: High => Undecided ** Changed in: ovn (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957817 Title: Multicast traffic is broken between VMs on different hypervisors using provider networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1957817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957817] Re: Multicast traffic is broken between VMs on different hypervisors using provider networks
** Changed in: ovn (Ubuntu) Status: New => Triaged ** Changed in: ovn (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957817 Title: Multicast traffic is broken between VMs on different hypervisors using provider networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1957817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961046] Re: Duplicate IP address on LSPs in the same LS lead to unpredictable flow output
Adding the OpenStack Neutron project to this bug after a discussion with the OVN team [4], which suggest that although the current OVN DB schema allows duplicates to occur it is the CMS's responsibility to avoid them. There is an related neutron bug 1960006 that did attempt to address a similar situation with stale ports in the OVN DB. However it does not appear to be sufficient to avoid this situation. I wonder if Neutron should do a pre-flight check along the lines of what the ``ovn-nbctl`` tool does [5]. 4: https://mail.openvswitch.org/pipermail/ovs-discuss/2022-February/051738.html 5: https://github.com/ovn-org/ovn/blob/ed81be75e8b3b33745eeb9b6ce2686b87ef72cd0/utilities/ovn-nbctl.c#L1392-L1433 ** Also affects: charm-ovn-central Importance: Undecided Status: New ** No longer affects: charm-ovn-central ** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961046 Title: Duplicate IP address on LSPs in the same LS lead to unpredictable flow output To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1961046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
