Current Series Release Notes¶
23.0.0-16¶
New Features¶
Added support for the OpenTelemetry tracing middleware provided by
oslo.middleware. The middleware is wired into the Aodh API paste pipeline and is disabled by default, acting as a zero-overhead passthrough when off. To enable distributed tracing, setenabled = Trueunder the[oslo_middleware_tracing]group inaodh.confand install the optional OpenTelemetry exporter packages, which ship as extras ofoslo.middleware:oslo.middleware[tracing-http]for the OTLP HTTP exporter oroslo.middleware[tracing-grpc]for the OTLP gRPC exporter. Enabling the middleware without these packages installed will cause the service to fail at startup.
The REST alarm notifier (
http,https,trust+httpandtrust+httpsactions) has two new options:[DEFAULT] rest_notifier_timeoutsets the timeout, in seconds, of the connection and of each read (300by default,0disables it), and[DEFAULT] rest_notifier_follow_redirects(Trueby default) can be set toFalseto stop following the HTTP redirections returned by the alarm actions.
Added
rest_notifier_tls_min_versionandrest_notifier_tls_max_versionoptions to control the TLS protocol versions used for HTTPS alarm action notifications. Accepted values are1.2and1.3. When unset, the system default applies.
Upgrade Notes¶
The WSGI script,
aodh-api, has been removed. Deployment tools should use python module paths (aodh.wsgi.api). In case the WSGI server doesn’t support python module paths, (for example mod_wsgi is known not to support it), create a.wsgiscript:import aodh.wsgi.api application = aodh.wsgi.api.application
The REST alarm notifier now uses a timeout of 300 seconds by default. It previously waited without limit for an alarm action that accepts the connection and never answers, which blocked the notification of the alarm. Set
[DEFAULT] rest_notifier_timeout = 0to restore the previous behaviour.
Security Issues¶
Bug #2167496: Fixed an authorization bypass in the alarm listing API where repeated
project_idquery filters made the authorization check operate on the first value while the storage query filtered on the last one, allowing a non-admin user to list another project’s alarms, including their action URLs. Repeated query fields are now rejected withHTTP 400.
Operators who do not want the notifications of the alarm actions, and the
X-Auth-Tokenheader of thetrust+httpandtrust+httpsactions, to be sent to a destination other than the URL of the alarm action can set[DEFAULT] rest_notifier_follow_redirects = False.
Bug Fixes¶
The alarm quota of a project set through the quota API (or created by the first
GET /v2/quotasof the project, which stores the default[api] project_alarm_quota) is now compared with the number of alarms of the project. It was compared with the number of alarms of the user creating the alarm, so each user of the project could create up to the project limit. A limit of-1set through the quota API now means no limit, as documented; it previously refused every alarm creation in the project.
23.0.0¶
Upgrade Notes¶
The deprecated
[oslo_policy] enforce_scopeconfiguration option has been removed in oslo.policy version 6.0.0 which will impact Keystone as there is no longer any way to disable RBAC policy scope enforcement; scope checks are now always enforced regardless of configuration.If you are not upgrading the oslo.policy to 6.0.0, then there will not be any change in scope enforcement behaviour.