- Release-announce - lists.openstack.org

xstatic-angular-smart-table 1.4.13.3
by no-reply＠openstack.org 13 Feb '26

13 Feb '26

We are chuffed to announce the release of: xstatic-angular-smart-table 1.4.13.3 The source is available from: https://opendev.org/openstack/xstatic-angular-smart-table Download the package from: https://pypi.org/project/xstatic-angular-smart-table For more details, please see below. Changes in xstatic-angular-smart-table 1.4.13.2..1.4.13.3 --------------------------------------------------------- 6e174e7 Bump package version a6c53bc Migrate to native namespaces 5404c75 OpenDev Migration Patch 6d35558 fix tox python3 overrides Diffstat (except docs and test files) ------------------------------------- .gitreview | 2 +- setup.cfg | 7 ------- setup.py | 5 ++--- tox.ini | 1 + xstatic/__init__.py | 1 - xstatic/pkg/__init__.py | 1 - xstatic/pkg/angular_smart_table/__init__.py | 2 +- 7 files changed, 5 insertions(+), 14 deletions(-)

1 0

oslo.service 4.5.0 (gazpacho)
by no-reply＠openstack.org 13 Feb '26

13 Feb '26

We contentedly announce the release of: oslo.service 4.5.0 This release is part of the gazpacho release series. The source is available from: https://opendev.org/openstack/oslo.service Download the package from: https://pypi.org/project/oslo.service Please report issues through: https://bugs.launchpad.net/oslo.service/+bugs For more details, please see below. 4.5.0 ^^^^^ New Features ************ * The oslo.service implements the required signal hanlders when service is launched in the main process. The below signals are captured and their respective handles are called: * "SIGTERM" * "SIGINT" * "SIGHUP" * "SIGALRM" * Added *oslo_service._multiprocessing* module providing "get_spawn_context()" and "get_spawn_pool()" utilities. These enforce the "spawn" start method to avoid fork-inherited lock deadlocks, as explained in: https://pythonspeed.com/articles/python- multiprocessing/ * The threading backend now supports the "spawn" multiprocessing start method. If a service is spawn-safe (picklable), "spawn" will be used as the default start method. Otherwise, the backend will automatically fall back to "fork" if available. This prevents inherited threading locks during worker respawn and improves compatibility with Python 3.12+. For more information about spawn-safe services, see spawn (https://docs.python.org/3/library/multiprocessing.html#contexts- and-start-methods). * Added new "register_service_opts" and "set_service_opts_defaults()" methods that allows OpenStack services to register and override a new default values for the below "service_opts": * "graceful_shutdown_timeout" * "log_options" Bug Fixes ********* * oslo.service SignalHanlder in "Threading" backend execute the signal handlers in a new thread, which does not work because the signal only works in the main thread. This issue has been fixed now by executing the signal handlers in the main thread. * Fixed a bug to launch the multiple workers with different service instance. If the first service instance was picklable the "spawn" multiprocessing context was selected. Any subsequent non-picklable service instance also used the "spawn" multiprocessing context and raised the error. The launcher now re-evaluates the spawn-safe service and if it is not spawn-safe then fallback to "fork" multiprocessing context. See bug 2141304 (https://bugs.launchpad.net/oslo.service/+bug/2141304) * In the threading backend, completed threads were never removed from the group's tracking. Long-lived services that repeatedly add threads could see unbounded growth. Completed threads are now removed when they finish, matching the documented behavior and eventlet. No caller changes needed. Changes in oslo.service 4.4.1..4.5.0 ------------------------------------ 360f1ac Run neutron-ovs-tempest-with-oslo-master job in check pipeline bf701c2 Fix service multiple workers launching different service instance 7c457ff Add register and set method to override the default value for service opts 131c462 Fix ServiceManager singleton race condition in tests 12dbe0b Fix race condition in EventletServerServiceLauncherTest ed7eb80 Fix unbounded growth of thread list in threading backend 325f30c Fix the followup comment from signalhander change 828aed5 Add signal handler for ProcessLauncher with no_fork 39adcef Refactor threading launchers to prefer spawn-safe multiprocessing 2d35d88 Fix race condition while creating the cotyledon.ServiceManager a2082aa Fix signal handler for threading mode 9ca3b4a Delay string interpolations at logging calls 419dcc7 Add multiprocessing utilities with spawn start method db8cde1 Remove reference to tag framework Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 3 + README.rst | 11 +- oslo_service/_multiprocessing.py | 125 +++++++++++ oslo_service/backend/_threading/service.py | 230 ++++++++++++++++++--- oslo_service/backend/_threading/threadgroup.py | 23 ++- oslo_service/eventlet_backdoor.py | 5 +- oslo_service/opts.py | 43 ++++ pyproject.toml | 2 +- ...-launched-on-main-process-51913add4552949f.yaml | 11 + ...-threading-signal-handler-4b396feab5d75db3.yaml | 7 + ...-unpicklable-second-service-crash-b2141304.yaml | 12 ++ ...rocessing-spawn-utilities-abaeb920e98b692d.yaml | 8 + .../notes/refactor-service-spawn-safe.yaml | 13 ++ .../notes/set_service_opts-fca7a4e8dbd4cdbf.yaml | 9 + ...oup-thread-done-auto-call-e64f74c8cd6c6d3c.yaml | 7 + test-requirements.txt | 2 +- tox.ini | 4 +- 25 files changed, 1113 insertions(+), 67 deletions(-) Requirements updates -------------------- diff --git a/test-requirements.txt b/test-requirements.txt index 2e8bc2b..618fe73 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -7 +7 @@ coverage>=4.0 # Apache-2.0 -cotyledon>=2.0.0 # Apache-2.0 +cotyledon>=2.2.0 # Apache-2.0

1 0

os-traits 3.6.0
by no-reply＠openstack.org 12 Feb '26

12 Feb '26

We are excited to announce the release of: os-traits 3.6.0 The source is available from: https://opendev.org/openstack/os-traits Download the package from: https://pypi.org/project/os-traits For more details, please see below. Changes in os-traits 3.5.0..3.6.0 --------------------------------- 15d22a7 CPU: add traits for new X86 feature "AMX" 0715f71 Drop basepython Diffstat (except docs and test files) ------------------------------------- os_traits/hw/cpu/x86/__init__.py | 4 ++++ tox.ini | 2 -- 2 files changed, 4 insertions(+), 2 deletions(-)

1 0

blazar 14.0.1 (dalmatian)
by no-reply＠openstack.org 09 Feb '26

09 Feb '26

We are ecstatic to announce the release of: blazar 14.0.1 This release is part of the dalmatian release series. The source is available from: https://opendev.org/openstack/blazar Download the package from: https://tarballs.openstack.org/blazar/ Please report issues through: https://bugs.launchpad.net/blazar/+bugs For more details, please see below. 14.0.1 ^^^^^^ Security Issues *************** * Fixes a bug where any user could update/delete a lease from any project, provided that they had the lease ID. When using the default policy configuration, there is no way for a regular user to see lease IDs of another project. However, operators that are running the Resource Availability Calendar may have overridden this policy, and so may be vulnerable without this fix. LP#2120655 Bug Fixes ********* * Fixes functionality of host randomization feature. LP#2099927 * Fixes an issue where the amount of instances in an instance reservation could not be updated when the lease is active. LP#2138386 Changes in blazar 14.0.0..14.0.1 -------------------------------- 2397617 Fix updating amount in active instance leases 2484089 Fix owner policy enforcement c05c4fa Fix lease date f1676c7 Fix host randomization 03630d9 Update TOX_CONSTRAINTS_FILE for stable/2024.2 d2fb210 Update .gitreview for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + blazar/plugins/instances/instance_plugin.py | 3 +- blazar/plugins/oshosts/host_plugin.py | 6 +- blazar/policy.py | 19 ++++- .../plugins/oshosts/test_physical_host_plugin.py | 6 +- .../fix-host-randomization-bcab5276ef6199e6.yaml | 5 ++ ...-owner-policy-enforcement-57a6d71c37ffec3d.yaml | 10 +++ ...-in-instance-reservations-52e6e3a413a0176f.yaml | 6 ++ tox.ini | 4 +- 11 files changed, 112 insertions(+), 51 deletions(-)

1 0

taskflow 6.1.1 (gazpacho)
by no-reply＠openstack.org 06 Feb '26

06 Feb '26

We are psyched to announce the release of: taskflow 6.1.1 This release is part of the gazpacho release series. The source is available from: https://opendev.org/openstack/taskflow Download the package from: https://pypi.org/project/taskflow Please report issues through: https://bugs.launchpad.net/taskflow/+bugs For more details, please see below. Changes in taskflow 6.1.0..6.1.1 -------------------------------- 6fc3a9b0 Avoid iterating over the same atoms in a graph 67b67db5 pre-commit: Bump versions Diffstat (except docs and test files) ------------------------------------- .pre-commit-config.yaml | 4 ++-- taskflow/engines/action_engine/traversal.py | 10 ++++++++++ taskflow/examples/99_bottles.py | 1 - 4 files changed, 26 insertions(+), 3 deletions(-)

1 0

cinder 25.3.1 (dalmatian)
by no-reply＠openstack.org 04 Feb '26

04 Feb '26

We high-spiritedly announce the release of: cinder 25.3.1 This release is part of the dalmatian release series. The source is available from: https://opendev.org/openstack/cinder Download the package from: https://tarballs.openstack.org/cinder/ Please report issues through: https://bugs.launchpad.net/cinder/+bugs For more details, please see below. 25.3.1 ^^^^^^ Bug Fixes * Bug #2111461 (https://bugs.launchpad.net/cinder/+bug/2111461) Fixed issue preventing cinder-manage command to purge deleted rows due to foreign key constraint errors. This happened as timestamp for bulk delete operations were recalculated per table resulting in slighty different intervals for deleting rows on primary and dependents tables. * HPE 3PAR driver Bug #2119709 (https://bugs.launchpad.net/cinder/+bug/2119709) Fixed: skip license check to work with new wsapi (of 2025). * Pure Storage driver bug #2096801 (https://bugs.launchpad.net/cinder/+bug/2096801) Fixed issue using Manage Volumes from the GUI. * Pure Storage bug #2101859 (https://bugs.launchpad.net/cinder/+bug/2101859) Fixed issue where LACP bonds were not been correctly identified as iSCSI and NVMe targets. * [Pure Storage] When using synchronous replication, ensure that FlashArray pods used by Cinder do not have SafeMode protection groups attached, as SafeMode is not supported by Cinder. * Bug #1886543 (https://bugs.launchpad.net/cinder/+bug/1886543) On retypes requiring a migration, try to use the driver assisted mechanism when moving from one backend to another when we know it's safe from the volume type perspective. Changes in cinder 25.3.0..25.3.1 -------------------------------- e70f1a858 Stop testing old release of cinder 90adabb67 HPE 3par - skip license check for new wsapi af4cb88a6 cinder-manage: Use same timestamp for purging deleted rows 49b5c010d Driver assisted migration on retype when it's safe 36e7d28cf zuul: cinder-plugin-ceph-tempest: raise swap size b9ac7315e [Pure Storage] Fix issue with LACP ports not being identified dfd9a8109 Huawei hypermetro: RECOVERYPOLICY typo 34590bec8 [Pure Storage] Remove SafeMode PGs from Replication Pods 1dde98deb [Pure Storage] Manage Volume from GUI fails 6f53af57d Always upload image volumes in a native thread Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 1 - cinder/db/sqlalchemy/api.py | 2 +- cinder/image/image_utils.py | 2 +- cinder/volume/drivers/hpe/hpe_3par_common.py | 7 +- cinder/volume/drivers/huawei/hypermetro.py | 2 +- cinder/volume/drivers/pure.py | 70 ++++++-- cinder/volume/manager.py | 36 +++- ...ign-key-constraint-errors-8a60db1f0158b36e.yaml | 9 + ...de-changes-for-wsapi-2025-75a9fda5d994504c.yaml | 4 + .../notes/pure-cinder-manage-aa40d62bf2bd0d33.yaml | 6 + .../notes/pure_lacp_iscsi-34678bdb98fa6bab.yaml | 7 + .../notes/pure_pod_safemode-d64b0705828529e5.yaml | 6 + ...retype-assisted-migration-6cdc7f9b21beb859.yaml | 7 + 18 files changed, 482 insertions(+), 112 deletions(-)

1 0

nova 30.2.1 (dalmatian)
by no-reply＠openstack.org 02 Feb '26

02 Feb '26

We are happy to announce the release of: nova 30.2.1 This release is part of the dalmatian release series. The source is available from: https://opendev.org/openstack/nova Download the package from: https://tarballs.openstack.org/nova/ Please report issues through: https://bugs.launchpad.net/nova/+bugs For more details, please see below. 30.2.1 ^^^^^^ Security Issues *************** * [bug 2131960 (https://bugs.launchpad.net/nova/+bug/2131960) Fixed improper teardown of Ironic nodes in servicing states. Previously, when Nova's virt driver called "destroy()" on Ironic nodes in certain states ("deploy hold", "servicing", "service wait", "service hold", "service failed"), these nodes would fail to undergo proper teardown, resulting in orphaned instances where instance metadata was removed but nodes remained unprovisioned in Ironic. In flat networking configurations, this could allow nodes traversing servicing states to briefly access tenant networks. In Neutron networking configurations, while VIFs would detach correctly, nodes would remain in Ironic with a shutdown IPA, and future deprovisioning attempts would fail due to missing networking metadata. These states are now properly handled to ensure complete node deprovisioning. Bug Fixes ********* * Nova operation with VIF type TAP was broken by a libvirt change (in 9.5.0) to treat TAP interface specifications as "managed" by default. This means that libvirt expects to create the TAP interface itself, which is incompatible with how Nova works, because Nova creates the TAP interface before telling libvirt about it. In particular this broke OpenStack with Calico as the network plugin, because Calico uses VIF type TAP. This is now fixed, by Nova adding the *managed="no"* attribute to TAP interface XML specifications. See bug 2033681 for more details. (https://bugs.launchpad.net/nova/+bug/2033681) * Fixed the issue bug 2044235 where Nova Conductor puts an instance into an error state if any errors occur during execution of the 'check_can_live_migrate_source()' method in an RPC call. Now, any error is caught and a MigrationPreCheckError exception is re-raised to reset the instance state. * [bug 2131960 (https://bugs.launchpad.net/nova/+bug/2131960) Fixed a bug where Ironic nodes in servicing-related provision states ("deploy hold", "servicing", "service wait", "service hold", "service failed") were not properly unprovisioned when instances were destroyed. The Nova Ironic virt driver now correctly triggers unprovisioning for nodes in these states, preventing orphaned node configurations in Ironic. Changes in nova 30.2.0..30.2.1 ------------------------------ 95c43bcf7c Replace removed os-vif-ovs job 60dfb55d94 Fix bug 2000069 19df809bb4 [ironic] Ensure unprovision happens for new states 8d95d55f77 Reset the mapped field of nodes at service deletion ab844a69c7 Adds regression test for bug LP#2085135 6a12fb1129 Update start_service() function in test 6a995e49fe Add managed='no' flag to libvirt XML definition for VIF type TAP f490c84d0f nova-conductor puts instance in error state 6e2926435e Adds regression test for bug LP#2044235 Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 2 +- nova/compute/manager.py | 23 ++++-- nova/db/main/api.py | 9 ++- nova/test.py | 17 ++++- .../functional/regressions/test_bug_2044235.py | 60 +++++++++++++++ .../functional/regressions/test_bug_2085135.py | 75 +++++++++++++++++++ .../functional/regressions/test_bug_2143972.py | 15 ++-- nova/virt/ironic/driver.py | 17 +++-- nova/virt/ironic/ironic_states.py | 38 +++++++++- nova/virt/libvirt/config.py | 8 +- nova/virt/libvirt/vif.py | 1 + ...type-tap-with-new-libvirt-791e8b5f170e9c40.yaml | 16 ++++ ...ance-after-rpc-issue-during-live-migration.yaml | 9 +++ ...-2131960-servicing-states-446d0e58bb9aa5f2.yaml | 25 +++++++ 20 files changed, 436 insertions(+), 49 deletions(-)

1 0

os-vif 3.7.1 (dalmatian)
by no-reply＠openstack.org 02 Feb '26

02 Feb '26

We are excited to announce the release of: os-vif 3.7.1 This release is part of the dalmatian release series. The source is available from: https://opendev.org/openstack/os-vif Download the package from: https://pypi.org/project/os-vif Please report issues through: https://bugs.launchpad.net/os-vif/+bugs For more details, please see below. Changes in os-vif 3.7.0..3.7.1 ------------------------------ a19f532 OVS Trunk: Add bridge_name to external_ids 7d4636e Do not add taps in trunk bridges to the dead vlan b39e995 Update TOX_CONSTRAINTS_FILE for stable/2024.2 8ee2f8f Update .gitreview for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + tox.ini | 4 +- vif_plug_ovs/ovs.py | 15 ++-- vif_plug_ovs/ovsdb/ovsdb_lib.py | 23 +++++- 7 files changed, 148 insertions(+), 11 deletions(-)

1 0

placement 12.0.2 (dalmatian)
by no-reply＠openstack.org 02 Feb '26

02 Feb '26

We are pumped to announce the release of: placement 12.0.2 This release is part of the dalmatian release series. The source is available from: https://opendev.org/openstack/placement Download the package from: https://pypi.org/project/placement Please report issues through: https://storyboard.openstack.org/#!/project/openstack/placement For more details, please see below. 12.0.2 ^^^^^^ Bug Fixes * Added a new config option "[workarounds]optimize_for_wide_provider_trees". It is disable by default. As reported in bug #2126751 in the situation where many similar child provider is defined under the same root provider, placement's allocation candidate generation algorithm scales poorly. This config option enables certain optimizations that help decrease the time it takes to generate the GET /allocation_candidates response for queries requesting multiple resources from those child providers. It should be enabled if you have at least 8 child resource providers within a tree providing inventory of the same resource class. And you are trying to support VMs with more than 4 such resources. E.g.: * Nova's PCI in Placement feature is enabled and you have at least 8 PCI devices with the same product_id in a single compute and you are using flavors requesting more than 4 such devices. * Nova's GPU support is enabled and you have at least 8 GPUs per compute node while requesting more than 4 per VM. You can keep it disabled if you have a flat resource provider tree, i.e. all resources reported on the root provider. Or if your flavors are not requesting more than 4 PCI or GPU resources of the same type. (https://bugs.launchpad.net/nova/+bug/2126751) Changes in placement 12.0.1..12.0.2 ----------------------------------- 8345235b Prune a_c search space by invalid prefixes 96e52a33 Reproduce GET a_c slowness bug/2126751 cab87078 Remove excessive logging from GET a_c Diffstat (except docs and test files) ------------------------------------- placement/conf/__init__.py | 2 + placement/conf/workarounds.py | 90 ++++++++ placement/objects/allocation_candidate.py | 81 ++++++- placement/objects/research_context.py | 14 +- .../unit/objects/test_allocation_candidate.py | 250 +++++++++++++++++++++ placement/util.py | 51 +++++ ...e_for_wide_provider_trees-b50b7813fd0d9dd2.yaml | 31 +++ 9 files changed, 733 insertions(+), 17 deletions(-)

1 0

os-vif 4.3.0 (gazpacho)
by no-reply＠openstack.org 02 Feb '26

02 Feb '26

We are delighted to announce the release of: os-vif 4.3.0 This release is part of the gazpacho release series. The source is available from: https://opendev.org/openstack/os-vif Download the package from: https://pypi.org/project/os-vif Please report issues through: https://bugs.launchpad.net/os-vif/+bugs For more details, please see below. 4.3.0 ^^^^^ New Features * Added support for os-vif to pre-create TAP devices when using OVS/OVN. The "VIFPortProfileOpenVSwitch" object now supports two new fields: * "create_tap": When set to "True", os-vif will create the TAP device with the correct MAC address and MTU before adding it to OVS. * "multiqueue": When set to "True" along with "create_tap", the TAP device will be created with multiqueue support enabled for improved performance with multiple vCPUs. The multiqueue setting is determined by Nova from the "hw:vif_multiqueue_enabled" flavor extra spec or image property. When the "[ovn]/ovs_create_tap" config option is enabled in Neutron's ML2/OVN mechanism driver, Neutron sets the "ovs_create_tap" flag in the vif_details during port binding. Nova then reads this value and propagates it to os-vif via the "create_tap" field, and configures libvirt with "managed="no"" so it uses the pre-created TAP device. This reduces live migration downtime by ensuring the network is fully wired before the VM starts. See bug 2069718 (https://bugs.launchpad.net/neutron/+bug/2069718) Changes in os-vif 4.2.1..4.3.0 ------------------------------ eba8007 Add TAP device pre-creation support for OVS/OVN 1c0a741 Fixed bridge name when per_port_bridge is used b4f277f Stabilize functional test 8427453 reno: Update master for unmaintained/2024.1 05bb255 Update master for stable/2025.2 134622b Remove remaining job with Ubuntu Jammy (22.04) Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 11 - os_vif/internal/ip/ip_command.py | 8 +- os_vif/internal/ip/linux/impl_pyroute2.py | 11 +- os_vif/objects/vif.py | 30 ++- .../internal/command/ip/test_impl_pyroute2.py | 111 +++++++++ .../unit/internal/ip/linux/test_impl_pyroute2.py | 66 +++++ .../add-tap-creation-support-2069718-abc123.yaml | 24 ++ releasenotes/source/2024.1.rst | 2 +- releasenotes/source/2025.2.rst | 6 + releasenotes/source/index.rst | 1 + vif_plug_ovs/exception.py | 6 + vif_plug_ovs/linux_net.py | 23 ++ vif_plug_ovs/ovs.py | 59 ++++- 18 files changed, 765 insertions(+), 30 deletions(-)

1 0