40b818b211
The oslo.service.wsgi.Server class is designed to work exclusively with the eventlet backend and is incompatible with the threading backend. This change adds backend compatibility checks to prevent improper usage and provide clear guidance to users. The error occurs immediately during Server instantiation, preventing potential runtime issues and guiding users toward proper deployment patterns. Applications using the threading backend should migrate to standard WSGI servers like uwsgi or gunicorn instead of relying on the deprecated oslo.service WSGI server. Assisted-By: Claude Sonnet 4 Change-Id: Ib31ea34fa435a14afbca9f9dafa9e88aab43da25 Signed-off-by: Hervé Beraud <hberaud@redhat.com>
20 lines
935 B
YAML
20 lines
935 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The ``oslo.service.wsgi.Server`` class now includes
|
|
backend compatibility checks to prevent improper usage with the threading
|
|
backend. Applications using the threading backend that attempt to
|
|
instantiate the WSGI Server will now receive an immediate
|
|
``UnsupportedBackendError`` exception with a clear error message.
|
|
|
|
This is an intentional breaking change to prevent potential runtime issues
|
|
and security concerns that could arise from using a component designed for
|
|
eventlet in a threading environment. The fail-fast behavior ensures that
|
|
applications using the threading backend are guided towards the correct
|
|
deployment patterns.
|
|
|
|
**Migration Path**: Users should migrate to deploying their WSGI
|
|
applications using standard WSGI servers such as ``uwsgi``, ``gunicorn``,
|
|
or similar alternatives instead of relying on the deprecated oslo.service
|
|
WSGI server.
|