I verified neutron 2:28.0.0-0ubuntu1.1 from resolute-proposed.

Environment:
- Ubuntu 26.04 LTS (Resolute), amd64
- Kernel 7.0.0-30-generic
- LXD virtual machine with 8 vCPUs and 24 GiB RAM
- regress-stack revision:
  5f21ed12d2f1820d08d527013803267fce7a6754
- Apache mod_wsgi with four neutron-api worker processes


The following Neutron packages were upgraded from
2:28.0.0-0ubuntu1 to 2:28.0.0-0ubuntu1.1:

- neutron-api
- neutron-common
- neutron-ovn-metadata-agent
- neutron-periodic-workers
- neutron-rpc-server
- python3-neutron


Baseline reproduction with 2:28.0.0-0ubuntu1:

- 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 as expected:

  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 from resolute-proposed:

- Two default segment ranges were initialized:
  - Geneve: 1-65535
  - VLAN: 1-4094
- Four distinct OVN hash-ring nodes were registered for the four
  mod_wsgi workers.
- All four nodes shared exactly 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-01 12:21:35 to
    2026-09-01 12:43:10;
  - four distinct nodes remained;
  - all nodes shared the new created_at value;
  - no IntegrityError or duplicate-key collision was logged.
- apache2, neutron-rpc-server, neutron-periodic-workers, and
  neutron-ovn-metadata-agent remained active.

I also ran the regress-stack Tempest selection (tempest tests are
upstream functional tests):

  Ran: 175
  Passed: 154
  Skipped: 21
  Failed: 0

The skips were capability/configuration skips, including unavailable
Swift/Cinder tests and Watcher microversions outside the configured
range.

I exercised the package test's mod_wsgi, segment-range, hash-ring, and
restart checks directly against the deployed cloud.


** Tags removed: verification-needed-resolute
** Tags added: verification-done-resolute

-- 
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

Reply via email to