I've also been able to verify the neutron caracal update for Jammy. Further testing information below.
Version tested: neutron-server 2:24.2.2-0ubuntu0.24.04.1~cloud0 Ran charmed-openstack-tester, results are attached. No failures due to neutron update, all in unrelated tests. Did individual verification of the following bugs: 1) https://bugs.launchpad.net/neutron/+bug/2069442 Issue was traceback seen intermittently when deleting VMs Verified changed code was present and neutron traceback didn't happen over multiple attempts creating/deleting instances in a loop, for example: while true; do openstack server create... openstack server delete... done Additionally, verified in the neutron server logs that this case was caught and logged as expected: sudo tail -f neutron-server.log | grep "Standard attribute was not found for port" 2026-11-04 16:25:41.027 1449565 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [None req-633b3f7e-a27b-4f52-83e1-0ae7a7a1bb3e - - - - - -] Standard attribute was not found for port 49315c61-faa6-4930-887c-d752647b4bc5. It was possibly deleted concurrently. _ovn_update_port /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py:882 2026-11-04 16:29:36.194 1449565 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [None req-633b3f7e-a27b-4f52-83e1-0ae7a7a1bb3e - - - - - -] Standard attribute was not found for port cb988ebe-ef88-4e7e-bd4d-5819cd0f5de0. It was possibly deleted concurrently. _ovn_update_port /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py:882 2026-11-04 16:32:38.981 1449566 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [None req-476ff2db-5c19-417f-b7dc-2c5d35d02404 - - - - - -] Standard attribute was not found for port d1ca86c3-a298-45eb-8a75-59a34b986961. It was possibly deleted concurrently. _ovn_update_port /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py:882 2026-11-04 16:32:48.149 1449565 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [None req-633b3f7e-a27b-4f52-83e1-0ae7a7a1bb3e - - - - - -] Standard attribute was not found for port c1af8d38-322b-4da5-8dcd-75e0d29c0905. It was possibly deleted concurrently. _ovn_update_port /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py:882 2) https://bugs.launchpad.net/neutron/+bug/2116087 Verified changed code was present and neutron port binding operates as expected. 3) https://bugs.launchpad.net/neutron/+bug/2032817 Issue was that mixed network MTU values would lead to traffic being dropped transiting the router/gateway node. First verified "need to frag" was set to true on neutron-api unit: plugins/ml2/ml2_conf.ini:ovn_emit_need_to_frag = True Then created some test resources from the undercloud: $ openstack network create foo $ openstack subnet create --network foo --subnet-range 10.2.0.0/24 foo $ openstack network create --mtu 1400 bar $ openstack subnet create --network bar --subnet-range 10.3.0.0/24 bar $ openstack router create foobar $ openstack router add subnet foobar foo $ openstack router add subnet foobar bar $ openstack router set --external-gateway ext_net foobar Verified on ovn-central node that the logical router port had the lower of the two mtus: $ sudo ovn-nbctl --no-leader-only list Logical_Router_Port 7de4e989-d1ec-4f13-bccd-27ae6a3211ea _uuid : 7de4e989-d1ec-4f13-bccd-27ae6a3211ea enabled : [] external_ids : {"neutron:is_ext_gw"=True, "neutron:network_name"=neutron-3aa62208-1bcd-4cd7-b8bf-a20d98fae6f9, "neutron:revision_number"="4", "neutron:router_name"="297c83c8-5630-4d5e-93e7-27a95bb6f15e", "neutron:subnet_ids"="c63a3148-06e9-40e2-92eb-6ff3012967f7"} gateway_chassis : [78d8cdc9-4cb7-4f37-8b40-26464ec18a16, dc9cb098-4ace-467d-9a0c-a750cadd2567, f4450d04-8ef2-4b0e-9b4c-3783a01e0034] ha_chassis_group : [] ipv6_prefix : [] ipv6_ra_configs : {} mac : "fa:16:3e:6e:b4:9f" name : lrp-7326be12-56a4-4807-a698-1c31705aa4f5 networks : ["10.159.0.126/25"] options : {gateway_mtu="1400", reside-on-redirect-chassis="true"} peer : [] status : {hosting-chassis=juju-929f75-zaza-8df205b5b847-29} "1400" here is correct, would have been 1442 without the fix. Launched two instances, one on each network, so one will have a larger mtu than the other. $ ./tools/instance_launch.sh 1 --image jammy --name foovm --network foo $ ./tools/instance_launch.sh 1 --image jammy --name barvm --network bar $ ./tools/float_all.sh Logged-into the VM with the larger mtu (foovm). Verified mtu settings: $ ip a s dev ens2 2: ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc fq_codel state UP group default qlen 1000 link/ether fa:16:3e:4b:e8:3f brd ff:ff:ff:ff:ff:ff altname enp0s2 inet 10.2.0.37/24 metric 100 brd 10.2.0.255 scope global dynamic ens2 valid_lft 42968sec preferred_lft 42968sec inet6 fe80::f816:3eff:fe4b:e83f/64 scope link valid_lft forever preferred_lft forever Then pinged the floating IP of the other VM, which has a smaller mtu: $ ping -s 1400 10.159.0.119 PING 10.159.0.119 (10.159.0.119) 1400(1428) bytes of data. From 10.2.0.1 icmp_seq=1 Frag needed and DF set (mtu = 1400) 1408 bytes from 10.159.0.119: icmp_seq=2 ttl=62 time=8.30 ms 1408 bytes from 10.159.0.119: icmp_seq=3 ttl=62 time=2.64 ms 1408 bytes from 10.159.0.119: icmp_seq=4 ttl=62 time=27.4 ms Frag needed message indicates fix worked correctly. Ping also succeeded. ** Attachment added: "openstack-jammy-caracal-results.txt" https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2148509/+attachment/6014973/+files/openstack-jammy-caracal-results.txt ** Tags removed: verification-caracal-needed ** Tags added: verification-caracal-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2148509 Title: [SRU] Neutron stable point releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2148509/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
