[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1107871: marked as done (unblock: neutron/2:26.0.0-3)

Your message dated Tue, 17 Jun 2025 20:32:52 +0000
with message-id <E1uRczE-004e3z-0o@respighi.debian.org>
and subject line unblock neutron
has caused the Debian Bug report #1107871,
regarding unblock: neutron/2:26.0.0-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1107871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107871
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: neutron@packages.debian.org
Control: affects -1 + src:neutron

Please unblock package neutron

[ Reason ]
The default threading configuration doesn't work with OVN setup.

[ Impact ]
OVN users will have a broken neutron-api server by default.

[ Tests ]
I'm constantly running a CI that does packaged-based deployment
and runs functional testing. I oberved no regression.

[ Risks ]
Very limited risk: only a configuration of the uwsgi config.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

Note: the package also contains corrected breaks for prior
versions of Neutron plugins.

unblock neutron/2:26.0.0-3

diff --git a/debian/changelog b/debian/changelog
index d452464043..5c14a9bf39 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+neutron (2:26.0.0-4) unstable; urgency=medium
+
+  * Fix breaks that should be using binary packages, not source.
+  * Configure default uwsgi configuration file so that neutron-api doesn't use
+    threads anymore, which was broken with OVN config (Closes: #1093303).
+
+ -- Thomas Goirand <zigo@debian.org>  Wed, 30 Apr 2025 13:44:34 +0200
+
 neutron (2:26.0.0-3) unstable; urgency=medium
 
   * Add more Breaks:
diff --git a/debian/control b/debian/control
index 788f1d766d..09d601e01a 100644
--- a/debian/control
+++ b/debian/control
@@ -517,9 +517,9 @@ Depends:
  ${misc:Depends},
  ${python3:Depends},
 Breaks:
- networking-bgpvpn (<< 22.0.0~),
- networking-l2gw (<< 1:21.0.0~),
- neutron-dynamic-routing (<< 2:26.0.0~),
+ python3-networking-bgpvpn (<< 22.0.0~),
+ python3-networking-l2gw (<< 1:21.0.0~),
+ python3-neutron-dynamic-routing (<< 2:26.0.0~),
 Recommends:
  iputils-arping,
 Description: OpenStack virtual network service - Python library
diff --git a/debian/neutron-api-uwsgi.ini b/debian/neutron-api-uwsgi.ini
index c287c6d01f..6a220bf8e2 100644
--- a/debian/neutron-api-uwsgi.ini
+++ b/debian/neutron-api-uwsgi.ini
@@ -40,13 +40,13 @@ close-on-exec2 = true
 ### Performance tuning ###
 ##########################
 # Threads and processes
-enable-threads = true
+enable-threads = false
 
 # For max perf, set this to number of core*2
 processes = 8
 
 # This was benchmarked as a good value
-threads = 32
+threads = 1
 
 # This is the number of sockets in the queue.
 # It improves a lot performances. This is comparable

--- End Message ---
--- Begin Message --- 
Unblocked.

--- End Message ---
Reply to: