I verified neutron 2:28.0.0-0ubuntu1.1~cloud0 from noble-proposed/gazpacho.
Environment: - Ubuntu 24.04.5 LTS (Noble), amd64 - Kernel 6.8.0-139-generic - LXD virtual machine with 4 vCPUs and 10 GiB RAM - Apache mod_wsgi with four neutron-api worker processes The following Neutron packages were upgraded from 2:28.0.0-0ubuntu1~cloud0 in noble-updates/gazpacho to 2:28.0.0-0ubuntu1.1~cloud0 in noble-proposed/gazpacho: - neutron-api - neutron-common - python3-neutron Baseline reproduction with 2:28.0.0-0ubuntu1~cloud0: - No default network segment range was initialized. - Only one of the four expected OVN mechanism-driver hash-ring nodes remained registered. - Creating a tenant network failed: POST /v2.0/networks HTTP/1.1 -> 503 "Unable to create the network. No project network is available for allocation." Results with 2:28.0.0-0ubuntu1.1~cloud0 from noble-proposed/gazpacho: - A default Geneve segment range (1-65536) was initialized. - Four distinct OVN hash-ring nodes were registered for the four mod_wsgi workers, all sharing one created_at value. - Tenant network creation succeeded: POST /v2.0/networks HTTP/1.1 -> 201 - The resulting network was ACTIVE and used Geneve segmentation ID 1. - After restarting Apache, created_at advanced from 2026-09-16 09:55:42 UTC to 2026-09-16 09:56:09 UTC; four nodes remained and shared the new value. No hash-ring collision was logged. - The API root returned HTTP 200. MySQL, RabbitMQ, OVN, and Apache were active, and dpkg --audit was empty. I also ran the regress-stack Tempest selection against the proposed packages on a separate Noble/Gazpacho VM (regress-stack revision 5f21ed12d2f1820d08d527013803267fce7a6754): Ran: 162 Passed: 153 Skipped: 9 Failed: 0 The skips covered unavailable Swift and Horizon capabilities, a single-compute topology, and Barbican configuration. Noble's packaged Tempest 36 could not run with Gazpacho's oslo.utils, so I used an isolated Tempest 46.3 runner. I set Tempest's Cinder catalog type to volumev3 to match the deployed service; the final full run passed. The manual mod_wsgi, segment-range, hash-ring, network-creation, and restart checks passed on the verification VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2150285 Title: Neutron 2026.1 with mod_wsgi packaging skips ML2 segment range initialization, causing tenant network creation failures To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/gazpacho/+bug/2150285/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
