This fixes the issue when a nested stack is serialized in
oslo.messaging and deserialization fails because we pass
a kwarg as an arg when we generate the exception remotely.
Templates can be complex and contain multiple instances of
map_merges. Debugging this can be complex, so this change
aims to improve the mapping and help users determine where
the problem has occured.
With this change, instead of just saying an error occured,
we will now return the object that the error occurred with
and a note about it's type. This will allow for quick
identification of what the problem was.
During volume detachment an instance can be in error state or locked.
Nova returns error 409.
Instance can be unlocked or fixed a bit later, but heat doesn't retry to detach volume.
The patch makes heat to retry detachments untill stack update timeout.
Magnum has deprecated it's Bay API and BayModel API a long ago and
these resource types were deprecated and are hidden in Heat now.
Magnum has removed the old API during Zed cycle and the resources are
no longer supported, so we should remove the implementation now.
oslo.db 12.1.0 has changed the default value for the 'autocommit'
parameter of 'LegacyEngineFacade' from 'True' to 'False'. This is a
necessary step to ensure compatibility with SQLAlchemy 2.0. However, we
are currently relying on the autocommit behavior and need changes to
explicitly manage sessions. Until that happens, we need to override the
Signed-off-by: Stephen Finucane <firstname.lastname@example.org>
that patch erroneously replaced dict.values() with dict.items(),
and now ExtraRouteSet can not be created due to AttributeError
('tuple' has no attribute 'has_interface').
ServerGroup resources work as scheduler hints for server
resources and replacement of it replaces the servers which
is undesirable in many circumstances.
- We don't allow update of ServerGroup resource properties
- If not created (CREATE_FAILED) without resource_id they will
- If does not exist in nova they would be created
- If exist in nova, FAILED resource status would be just
changed to COMPLETE
Earlier users had to specify merge strategy for
a parameter/parameter_default in every environment
file where they are used(or the defaults for that
environment was used). However, the strategy
for a parameter in the first environment was
ignored as there is nothing to merge.
With Iec3367667248d0b46196a6d569f3cbb3b200d842, we
changed to use existing merge strategies, but the
strategies in the first environment were still
ignored. This patch fixes it.
The importlib-metadata package was imported to the core Python since
Python 3.8, and stevedore uses the standard library implementation
instead of the 3rd party package in Python 3.8 and later. However
the implementation available in Python 3.8 is quite old and especially
it does not include the change which added the module attribute.
This change makes sure we avoid referring to that attribute if it does
not exist, to avoid AttributeError in Python 3.8.
Since sqlalchemy 1.4.14, the following warning is raised unless
the cache_ok flag is explicitly set in classes inheriting
SAWarning: TypeDecorator Json() will not produce a cache key because
the ``cache_ok`` attribute is not set to True. This can have
significant performance implications including some performance
degradations in comparison to prior SQLAlchemy versions.
Set this attribute to True if this type object's state is safe to use
in a cache key, or False to disable this warning. (Background on this
error at: https://sqlalche.me/e/14/cprf)
Because the flag was set to True by default in older releases, this
adds explicit cache_ok = True, to restore the previous behavior in
Wallaby and older. (wallaby u-c has SQLAlchemy===1.3.23 while xena u-c
This patch adds a new resource to support ``minimum_packet_rate_rule``
QoS rule in Neutron.
We don't allow different parameter merge strategies
in different environment files for a parameter. If
a merge strategy has already been provided in one
environment file, let's use that for subsequent ones
unless a different merge strategy has been provided.
Using the healthcheck middleware as a filter is deprecated and
the middleware should be used as an application.
This change updates definition and usage of the healthcheck middleware
accordingly to avoid the following deprecation warning.
DeprecationWarning: Using function/method 'Healthcheck.factory()' is
deprecated: The healthcheck middleware must now be configured as
an application, not as a filter.
This also refactors composite definitions based on flavor by the new
This change adds validation of the limit query parameter in List
Software Config API, as was implemented for List Stack API, to avoid
internal error at database query.
The CloudWatch API was removed during Queens cycle. This change
removes the remaining parameters because these have been kept for
enough cycles to let users aware of the removal.
In some cases, some resources may require more than
one service_extension. In this case, we should allow
resources to define a list of required resources.