Debian Patches
Status for cinder/2:29.0.0-4
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| install-missing-files.patch | Install missing files | Thomas Goirand <zigo@debian.org> | not-needed | 2016-03-22 | ||
| do-not-use-urllib3-from-botocore.patch | Do not use urllib3 from botocore Cinder is using urllib3 vendored version from botocore, which we unvendor in Debian. =================================================================== |
Thomas Goirand <zigo@debian.org> | no | 2026-09-12 | ||
| add-params-thin_provisioning-equal-one.patch | Add "params thin_provisioning=1" in tgt export Add 'params thin_provisioning=1' in iscsi volume export to allow fstrim to work with the lvm backend. |
Thomas Goirand <zigo@debian.org> | yes | 2023-12-04 | ||
| fix-db-schema-migration.patch | Fix db schema migration This is a known issue documented here: https://bugs.launchpad.net/cinder/+bug/2070475 |
Thomas Goirand <zigo@debian.org> | no | 2024-11-20 | ||
| Fix-evaluator-for-pyparsing-3.3.3.patch | Restrict evaluator fn operator to actually implemented functions pyparsing 3.3.3 replaced the recursive implementation of infixNotation with a shunting-yard parser, in which unary operators with OpAssoc.RIGHT are now treated as generic prefix operators. The evaluator grammar defined fn = Word(alphas + '_' + '.') as such an operator to implement function calls, which now makes pyparsing capture any bare identifier as a function applied to the rest of the expression: dotted variable references such as stats.free_capacity_gb or capabilities.foo, as well as the NOT keyword, can no longer be substituted, breaking the DriverFilter and GoodnessWeigher, and failing 14 unit tests at build time. . Restrict the fn operator to the only functions that the evaluator implements (abs, max, min): any other name was already failing with a KeyError at evaluation time, so this only affects the error path. The parser now behaves identically with pyparsing 3.0.9, 3.1.2 and 3.3.3. =================================================================== |
yes | debian | 2026-10-11 | ||
| CVE-2026-93856_Fix_cross-project-info-disclosure-in-messages-API.patch | Fix cross-project information disclosure in the messages API Make the default for project_only=True in _messages_get_query() in the db api, so a 'member'/'reader' user making the "List messages" call of the Block Storage API v3.3 no longer sees other projects' non-expired user messages in the response (CVE-2026-93856). diff --git a/cinder/db/api.py b/cinder/db/api.py index 100269396..ecd82fa05 100644 |
Rajat Dhasmana <rajatdhasmana@gmail.com> | yes | debian upstream | upstream, https://review.opendev.org/c/openstack/cinder/+/1011487 | 2026-10-20 |
| fix-test-hitachi-replication-test-fixture-poisoning.patch | Work on copies of shared fixtures in Hitachi replication tests test_get_failback_volume_update_snapshot_error sets the "snapshots" field on the module-level TEST_VOLUME[6] fixture object in place, leaving it set for the rest of the worker process. Whenever test_failover_host_failback runs in the same process afterwards, the leaked snapshot (TEST_SNAPSHOT[5], secondary site) is saved and fails with SnapshotNotFound because that row does not exist in the per-test database, breaking the build. . Use deepcopy'd copies of the fixture objects at the use site, as test_hitachi_hbsd_rest_fc.py already does for TEST_SNAPSHOT[0]. =================================================================== |
yes | 2026-11-08 | |||
| fix-test-vastdata-factory-poisoning.patch | Stop polluting the VastData resources factory in tests TestVastResourceEntry instantiates FakeVastResource, whose __init__ registers "test_resource" into the process-wide VAST_RESOURCES_FACTORY for the remaining life of the worker process. Whenever TestSession.test_undefined_vast_resource runs in the same process afterwards, the request for that resource no longer hits the "factory not found" assertion, so the expected AssertionError is never raised and the test fails. . Pop the resource from the factory again in the test cleanup. =================================================================== |
yes | 2026-11-08 | |||
| fix-test-pure-manageable-snapshot-refs.patch | Work on copies of the Pure manageable snapshot fixtures test_get_manageable_snapshots_already_managed mutates the first entry of the module-level MPS and MPS_REFS fixtures in place, as it only takes shallow copies of the fixture lists. The mutations outlive the test, so whenever test_get_manageable_snapshots runs afterwards in the same worker process, its pristine expectations no longer match the poisoned fixtures and the test fails. . Take deep copies of the fixture lists instead, as the sibling volume tests already do for MPV and MPV_REFS. =================================================================== |
yes | 2026-11-08 | |||
| CVE-2026-pending_OSSA-2026-051_Disallow-invalid-IQNs-in-Cinder-iSCSI-targets.patch | Disallow invalid IQNs in Cinder iSCSI targets Block initiator IQNs containing invalid characters for iSCSI volume targets managed by cinder-volume, so that a path traversal within the connector's initiator element cannot create or overwrite files in the volume host filesystem (CVE-2026-pending). The check is done in rtstool.py to cover the specific case described in the bug, and also in volume/targets/iscsi.py to standardize it across other targets. diff --git a/cinder/cmd/rtstool.py b/cinder/cmd/rtstool.py index ed5a758..81d6c97 100644 |
Eric Harney <eharney@redhat.com> | yes | debian upstream | upstream, https://review.opendev.org/c/openstack/cinder/+/1015485 | 2026-11-17 |
All known versions for source package 'cinder'
- 2:29.0.0-4 (sid)
- 2:29.0.0-3 (forky)
- 2:26.0.0-2 (trixie)
- 2:21.3.1-1~deb12u1 (bookworm-security, bookworm)
