Debian Patches
Status for python-oslo.service/4.8.0-4
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| install-missing-files.patch | install all files | Thomas Goirand <zigo@debian.org> | no | 2026-02-25 | ||
| make-it-work-with-latest-oslo.config.patch | Make it work for latest oslo.config | Thomas Goirand <zigo@debian.org> | no | 2026-08-23 | ||
| Threading_backend_notify_systemd_of_readiness_with_no_fork.patch | Threading backend: notify systemd of readiness with no_fork ProcessLauncher in the threading backend runs the service in the main process when launched with no_fork=True, but unlike the eventlet backend it never calls systemd.notify_once(), so no READY=1 is ever sent. Services started this way (e.g. nova-compute) hang in "activating (start)" state until TimeoutStartSec expires and are then killed when the unit uses Type=notify. . Send the readiness notification after the service start() succeeds in the no_fork branch. Services using the cotyledon-based launchers already notify via ServiceManager.run() and are unaffected. diff --git a/oslo_service/backend/_threading/service.py b/oslo_service/backend/_threading/service.py index 1f7a949..34c2b7b 100644 |
Thomas Goirand <zigo@debian.org> | yes | 2026-09-16 |