2026.1 Series Release Notes

26.0.0

Nouvelles fonctionnalités

  • Added support for auto as a valid value for the gateway_ip property in the OS::Neutron::Subnet resource. This allows Heat templates to explicitly specify auto. Note that auto can only be used during subnet creation; it is not supported when updating an existing subnet.

  • Stack abandon action is now convergence aware. When convergence engine is enabled, abandoning a stack now uses the convergence workflow for resource cleanup, allowing for better parallelism and consistency with other stack operations. Physical resources are retained (not deleted) while Heat’s database records are cleaned up through the convergence flow.

  • Stack check action is now convergence aware. When convergence is enabled, stack check will traverse through all resources using the convergence engine instead of the legacy sequential approach. This allows check to continue processing remaining resources even if some resources fail their check, providing a complete picture of the stack’s health.

  • Stack snapshot and restore actions are now convergence aware. Snapshots are integrated into the convergence dependency graph, enabling non-blocking snapshot deletion during stack delete operations. This improves performance by allowing snapshot cleanup to be processed in parallel with the convergence workflow rather than blocking the entire operation.

  • Stack suspend and resume actions are now convergence aware. These actions are fully supported by convergence mode.

  • The block_device_mapping_v2 property of the OS::Nova::Server resource now supports the volume_type parameter. This allows users to specify the Cinder volume type when creating volumes from images, snapshots, or blank sources during server creation, eliminating the need to create separate OS::Cinder::Volume resources.

    This feature requires Nova API microversion 2.67 or later. When using volume_type with an older Nova API version, Heat will return a validation error.

  • The OS::Neutron::RBACPolicy resource now supports additional object types beyond network and qos_policy, including security_group, address_scope, and subnetpool.

    All new object types support the access_as_shared action.

Notes de mises à jours

  • The RPC API version has been bumped to 1.37 for the engine service and 1.6 for the worker service to support the convergence-aware stack check feature. Operators performing rolling upgrades should ensure all heat services are upgraded together.

  • A new database table resource_snapshot has been introduced to store per-resource snapshot data for convergence mode. This table is automatically created during database migration.

Deprecation Notes

  • The [ec2authtoken] auth_uri option was deprecated in favor of keystoneauth options added to the same section.

  • The [ec2authtoken] allowed_auth_uris option was deprecated in favor of new [ec2authtoken] clouds options and [ec2authtoken.<name>] sections.

  • The following options in the [ec2authtoken] section have been deprecated.

    • ca_file: Use cafile

    • cert_file: Use certfile

    • key_file: Use keyfile

  • The OS::Vitrage::Template resource is now deprecated. The vitrage project was marked inactive.

Corrections de bugs

  • The Keystone v3 ec2token end point requires authenticated access. The Heat ec2token filter now requires Keystone auth settings to be able to verify EC2 credentials. For single cloud mode the ec2token filter will look in the [ec2authtoken] section of the heat configuration for keystone authentication settings.

    In multicloud mode keystone auth settings must be supplied in configuration file sections names [ec2authtoken.<name>] . The [ec2authtoken] clouds option should be also configured to define the list of names.

    Note that ec2token request will be sent without authentication if the legacy settings (auth_uri and allowed_auth_uris) are still used.

  • The disk_bus property of OS::Nova::Server resource’s block_device_mapping_v2 now accepts “sata” as a valid value. The SATA disk bus was added to Nova in the Queens release. See story 2011600.

  • Fixed an issue where long error messages from external services (such as Nova errors containing large base64-encoded user_data) would exceed MySQL’s TEXT column limit (65,535 bytes) when being stored in the status_reason field. This caused database constraint violations that left resources in inconsistent states with unreleased locks, preventing stack DELETE operations from completing. The database layer now truncates status_reason to 65,535 bytes when using MySQL to prevent this issue. See story 2011188.