Current Series Release Notes¶
33.0.0-42¶
Prelude¶
The deprecated
sqliteimage cache driver has been removed. Theimage_cache_sqlite_dboption remains temporarily supported only to locate the legacy SQLite database during migration to centralized_db. It no longer selects a cache driver and should be removed after migration.
New Features¶
Adds the
GET /v2/info/import/detailAPI for administrators and service users. The response includes the supported import methods and the configured image import plugins, including safe plugin configuration details exposed by Glance.
A new configuration option
[image_format]/allowed_upload_formatscontrols which disk formats may be used with traditional image upload (PUT /v2/images/{id}/file). When left empty (the default), behavior is unchanged: anydisk_formatallowed at create time may be uploaded. When set to a non-empty list, traditional upload is rejected with HTTP 400 unless the imagedisk_formatis in that list.This lets operators keep formats such as
qcow2indisk_formatsso interoperable image import and the image conversion plugin can use them as the declared source format, while blocking those formats on the traditional upload path (which does not run conversion).Restricting who may call traditional upload remains the role of the
upload_imagepolicy.allowed_upload_formatsonly limits formats when configured with a non-empty list. The three related settings work independently:[image_format]/disk_formats– formats allowed at image create[image_format]/allowed_upload_formats– formats allowed forPUT /file[image_conversion]/output_format– format stored after conversion
Added support for the OpenTelemetry tracing middleware provided by
oslo.middleware. The middleware is wired into the Glance 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 inglance-api.confand install the optional OpenTelemetry packages.
Store discovery now reports
read_randomfor each configured backend. For backends that support ranged reads, the response also includesmax_concurrent_range_requests. The newmax_concurrent_range_requestsoption controls the advertised per-worker limit.
Upgrade Notes¶
No behavior change on upgrade.
allowed_upload_formatsdefaults to empty, which applies no extra restriction. Operators who want the new behavior must set a non-empty list intentionally.
Starting with the 2027.1 release, the deprecated Image API
/v2/tasksendpoints and their schema endpoints return410 Gone. Use the interoperable image import API andGET /v2/images/{image_id}/tasksinstead.The public Tasks API was deprecated in Mitaka, has not been available to non-admin users by default, and has not had meaningful test coverage for at least three years. The following policy rules are removed and should be deleted from customized policy files:
get_taskget_tasksadd_taskmodify_tasktasks_api_access
The internal task machinery used by the interoperable image import workflow is unchanged. Compatibility routes remain only to return
410 Gone.
The
digest_algorithmoption has been removed, as it had no effect.
The
metadata_encryption_keyoption and its underlying feature has been removed. It had been deprecated in the D release and was supposed to be removed in the F release.
The
sqlitecache driver has been removed in this release. Theimage_cache_sqlite_dbconfiguration option has also been removed.
Security Issues¶
Fix a security issue allowing attackers to decompress “Zip bombs” using the decompression plugin used by the image import workflow. While using Zip and Gzip files is now safe, it is strongly discouraged to use LHA files, as they are still vulnerable.
Glance now handles client disconnects while reading chunked image uploads. Previously, a socket error raised by uWSGI after the client disconnected was reported as an internal server error. The image is restored to the queued state and the API returns a client error instead. The packaged Apache configuration also answers
Expect: 100-continueitself, preventing clients from waiting for uWSGI to send the interim response before streaming a request body.
A bug in the
glance-downloadimport method (used to copy an image from another Glance region,POST /v2/images/{image_id}/import) was fixed which allowed an unbounded amount of data to be read from the remote region’s/v2/images/{image_id}/fileendpoint. A malicious or misbehaving remote region could report a small, believable size on the earlier, independent image metadata call, but then return far more data (or never terminate its response) when the file itself was fetched, keeping a task worker busy indefinitely and consuming unbounded local staging space. The download now honors the existingimage_size_caplimit, aborting once more than that many bytes have been read, the same protection already applied to other image-data ingestion paths (see theweb-downloadfix in bug 2160020). Note that the default value for this limit is 1TiB, which may be higher than is reasonable for some deployments. Operators should take this opportunity to review that setting for correctness.
Also fixed a related bug in the
glance-downloadimport flow’s failure handling: if the download step failed after the image metadata step had already run, reverting the flow could raise an unrelatedInvalidImageStatusTransitionerror (attempting to move the image fromqueuedtoqueued), which masked the real failure reason in the task record. The image now reverts toqueuedcleanly regardless of ordering.
A bug in the
location_importflow used byPOST /v2/images/{image_id}/locationswas fixed which allowed the background secure-hash calculation (do_secure_hash, enabled by default) to read an unbounded amount of data from the image location. A malicious or misbehaving remote location could report a small, believable size when the location was validated, but then return far more data (or never terminate its response) when the data was actually fetched for hashing, keeping a task worker busy indefinitely. Hash calculation now honors the existingimage_size_caplimit, aborting once more than that many bytes have been read, the same protection already applied to other image-data ingestion paths (see theweb-downloadfix in bug 2160020). Note that the default value for this limit is 1TiB, which may be higher than is reasonable for some deployments. Operators should take this opportunity to review that setting for correctness.
Bug Fixes¶
- Bug 2172280:
Fixed
image_size_capnot being honored against thevirtual_sizeof images being converted from such formats to raw. This could allow inflating a very small image into images much larger than the desired limit.
Image download now returns HTTP 503 instead of HTTP 500 when a configured store backend is unavailable.
33.0.0¶
Bug Fixes¶
Fix a regression introduced when fixing CVE-2026-71197. Now during image import via web-download, if the image host is resolved to several IP addresses by DNS, all of them that pass filtering critera will be tried one by one.
This among others ensures that if DNS resolves to both IPv4 and IPv6 addresses but Glance itself is running in a single stack network, the correct IP address that Glance can connect to will eventually be tried.