When generating the node_data() for a resource, catch and store any
exceptions (other than InvalidTemplateAttribute) encountered while
getting attributes. Re-raise the exception at the point where we try to
read the attribute value, including where we try to serialise the
NodeData object to store in the database.
In convergence, we generate and immediately serialise the NodeData, so
this should result in no substantial change in behaviour there.
In other situations (e.g. when we're just loading the data to show the
stack), this prevents an error in attribute calculation from aborting
the whole operation. The exception will still be raised if (and only if)
the erroneous attribute is accessed, but may be handled more
appropriately. For example, errors in calculating output values are
handled by reporting an error only for that particular output.
Change-Id: Idc97aee87405cc13e83be3373078b52e725850ea
Co-Authored-By: Zane Bitter <zbitter@redhat.com>
Closes-Bug: #1712280
The 5.32.0 release of oslo_messaging included the following change to the
Fake driver:
https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=d1dac1c11d357aa8391de7e62f4d003eb820948d
Which means that FakeExchanges are now shared between all
FakeExchangeManager instances. This broke the unit tests in Heat.
This patch effectively reverts the change in oslo_messaging by isolating
FakeExchanges to individual FakeExchangeManger instances once more.
Change-Id: I6c53f477b17247958be7bd6056136bc9f7f50865
Closes-Bug: #1718780
When deleting the snapshot image for server resource,
we didn't use the correct client plugin, to use
'glance' instead of 'nova'.
Change-Id: I2c0e72cd6819ba2b1e27308a32b59f020804fcfd
We override the method get_reference_id() for
scaling policy by calling the supper method, remove it.
Change-Id: Ia205ffebc4c9260445336127ad0bf0f38cf6508f
Adds property 'domain' for keystone role
resource:
1. the default value of the property is 'default'
2. the property is non-updatalbe
Change-Id: I829921dc35e2754eb6c6ccc293423c755806b0df
Closes-Bug: #1684558
It's been possible to set tags for the Mistral workflows, this
change adds a 'tags' property to the resource to make that possible
from Heat.
Change-Id: I231b3619eca86214ecbf33b05651c1b08cfddf96
Related-Bug: #1715389
We started to use keyston esession with mistal client plugin
since pike, but it seems the patch to translate keystoneauth
exceptions to mistal api exceptions did not get to
python-mistalclient==3.1.2.
Change-Id: I198cdbb8ee02623f2f5fb03a784135ce6f94a046
Closes-Bug: #1714679
Removing the uwsgi config files on stop breaks upgrades when using
uwsgi, so let's not do that. Keeping the file deletes in cleanup
makes sense and those calls remain.
Change-Id: I603754c3f5ed5d2f143cf789df96018ec99ad692
This isn't actually used and is a leftover from a thing we did
seven years ago that survives today through copy-pasta.
Change-Id: I7fed29322e00fa72b949692e01d821faa3f718ba
tl;dr : without this Pike and Queens have the same version causing
packaging issues.
https://docs.openstack.org/developer/pbr/#version
Because projects don't push a tag before milestone 1 (queens-1
here), downstream packages are still building packages by using the
version from Pike and it causes problems to distros because they
can't test the upgrades from Pike to Queens.
Bumping the semver will allow us to test packages upgrades.
Note: When your version is X.Y.Z, api-break will bump X, and feature
will bump Y. In this patch, we bump X because this is the way you
bump tags over releases.
Change-Id: I3036486835b4605be3e3891fc5be971fcd834199
Sem-Ver: api-break
Cinder returns the volume infos with key 'readonly',
not 'read_only', so parse live data with correct key
'readonly' for volume resource.
Change-Id: If19db3129f23a6cb9d19e6744c4ffc4522166426
Closes-Bug: #1712041
Thomas Herve