As a transition strategy to running heat_integrationtests as a
tempest plugin, this change puts the test config values in the
"heat_plugin" section. This will allow for either test runner
to be used during the transition.
blueprint tempest-plugin-support
Change-Id: I2eab50be92c998aeb1ee98011908a9828a7efe6c
Currently str_split raises error, when function take string to split as
NoneType object (e.g. get_attr value during validation). Fix such
behaviour to allow resources with str_split in properties pass
validation.
Change-Id: Iabd8ebb90a38253434e7c29005654c9a6abb3196
Closes-bug: #1608482
Gate logs for heat jobs really need to log stack traces with TRACE
instead of ERROR because some traces are being printed by passing
exc_info=True to LOG.info so they are not actual errors.
TRACE should be the default for oslo.log but something in the gate
setup is setting it to ERROR. Setting explicitly here restores the
desired pattern and protects against gate default overrides.
Change-Id: Id85287324fa6dc79d67fb1ed37c3f256d661133e
Closes-Bug: #1606404
We want to be able to use the internal API to gracefully cancel a create
operation that is in progress. (Users can still use the stack-cancel-update
command only to cancel an update, not the initial creation of a stack.)
Change-Id: I204f13d9ed7b826c6c5ac94126e23f2ed6d7e97f
Related-Bug: #1591341
The code designed to deal with the case where an in-progress StackResource
update is cancelled by stopping the update of the nested stack has never
worked because it was erroneously trying to catch StopIteration exceptions
instead of the actual exception raised when a generator is closed,
GeneratorExit.
This change moves the handling code to the new handle_update_cancel()
mechanism instead. Using this mechanism also means that StackResources will
be cancelled immediately, rather than waiting for up to error_wait_time
before cancelling the nested stack update. The previous patch adds a grace
period for IN_PROGRESS resources within the nested stack to complete, so we
want to notify it straight away to begin that period (and to not start any
new work).
Since the grace period on the child stack means that the child is likely to
still be IN_PROGRESS at the time we want to roll back, handle rollback by
sending an update-cancel with rollback message to the child. Only if the
child is no longer IN_PROGRESS will we start an update with the previous
template. If it is still IN_PROGRESS then just wait for it to reach
ROLLBACK_COMPLETE.
Change-Id: Ide210f695446fe8de2057b3b74c276165a6f9f3f
Closes-Bug: #1591337
Closes-Bug: #1446252
When we create the internal port on a nova server, we shouldn't pass
value_specs when specifying extra properties, as it's an internal
dictionary which is not accepted by the API.
Change-Id: I0bb4407e89b5575dbaf8f198402e0926b550224d
Closes-Bug: #1607364
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: Ie64b63a462ae9b2c25ce9ab9e05259350353522e
This adds a new test which actually trigger the 'is_using_neutron'
resource method by creating a server using a port.
Change-Id: Ic9a3f42fa5b24048472256832496eb630cdba2c9
Neutron v2 client wraps SessionClient and it's
available as an attribute `httpclient'.
Change-Id: I664be1b00975b048e2289f5be3270b4a00520e80
Closes-Bug: #1607222
It seems at times it takes more time than the current default
for the child processes to exit normally. Increasing it to
120 seconds.
Change-Id: Ic54d2d7edc97cbe07ed4a4445cb865bd1b157f9d
Closes-Bug: #1607177
swiftclient doesn't use oslo_log and logs ERROR with TRACE for
response exceptions like 404. This isn't desirable for heat which
relies on 404s to know a delete is complete.
This change sets the swiftclient logging level to CRITICAL in the
client plugin.
Change-Id: Ie11a6d19068169424ee883ce428aad306d647f0d
Partial-Bug: #1606404
