The node key in the convergence graph is a (resource id, update/!cleanup)
tuple. Sometimes it would be convenient to access the members by name, so
convert to a namedtuple.
Change-Id: Id8c159b0137df091e96f1f8d2312395d4a5664ee
The gate has started failing due to interface detaches timing out.
Examining the logs, it looks like Nova's interface detach retry takes about
6s to run one attempt. Heat, on the other hand, does 10 retries at 0.5s
intervals. So if Nova has to retry then Heat will fail.
Increase Heat's polling interval to make it more likely that if Nova
succeeds, Heat will see it.
Change-Id: Ie74980a3f806b8c17e4e494ae979725b0078f135
Closes-Bug: #1585858
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
In order to make it simpler to use the default
configuration files when deploying services
from source, the files are added to pbr's
data_files section so that the files are
included in the built wheels and therefore
deployed with the code. Packaging and deployment
tools can then more easily use the default files
if they wish to.
This pattern is already established with similar
files for neutron, designate and glance as has
been mentioned in the related bug report.
Change-Id: I1f3c9b2e27d44f28f0e649e2c96a1c3dc1da9ea6
Closes-Bug: #1718356
UpdateWaitConditionHandle docstring tells it is identical
to WaitConditionHandle without specifying that it inherits
from aws_wch.WaitConditionHandle.
This is confusing as Heat::WaitConditionHandle is called
via curl_cli while Heat::UpdateWaitConditionHandle should
be called via cfn-signal.
Change-Id: I48d6cc8ebbc754c89befb0281b9097e964c21a49
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 only have to remove the existing snapshots
for resources when stack delete.
Change-Id: Ia195f3c3380fe71e0888c8291209dd4562318951
Closes-Bug: #1716612
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
Zane Bitter