There are some test cases that still use the
test.HeatIntegrationTest base class instead of
the functional_base.FunctionalTestsBase base class.
The effect is that these tests will not check whether
they are skipped (e.g. by setting the
heat_plugin/skip_functional_tests oslo.config attr)
and in some cases end up being executed and reporting
false errors.
Change-Id: I074901f4d0c0c84fa09554e09095402fb9cf0b8e
Closes-Bug: #1699124
setUp and tearDown will be automatically called around each
testcase, so this is to remove setUp and tearDown that doing
nothing additional than super to keep code clean.
Change-Id: I8b6943602419d3f360991721d90b61888b55ea60
When updating a stack with the existing flag, we keep the parameters
from the old template to be used against the new version. Sometimes
parameters will get remove and won't make sense anymore, and keeping
them would break update with a 'Parameter was not defined' error. This
filters out such parameters so that the updates succeed.
Change-Id: I6f2aa77da28d271dd001a137bb574b5470292f15
Closes-Bug: #1558610
yaml.load() provides the ability to construct an arbitrary python object
that may be dangerous. yaml.safe_load() limits this ability to simple
python objects like integers or lists.
ref: https://en.wikipedia.org/wiki/YAML#Security
Change-Id: I9c28c25f4265fb691d39e72e20ef9c99f5538bf5
When an update fails on a template resource, we still store the template
in the stack environment. Retrying the update will fail because of
missing parameters, but we can ignore those as they should be harmless
and only matter in this broken case.
Change-Id: I859ea72b1cc95162b6f498b6af65e4d9fdd9458f
Closes-Bug: #1543685
Splits the existing abandon action into two actions as
below:
1. export: User is recommended to run export successfully
before doing the abandon action. It returns the stack
data, which can be used for adopting stack.
2. abandon: Abandons the given stack
Partial-Bug: #1353670
Co-Authored-By: Jason Dunsmore <jasondunsmore@gmail.com>
Change-Id: I65264d91b1378df9cb3e492bc6ccaa778940dd6b
This adds options to skip scenario and functional tests.
You can either skip the complete set of tests or list of specific
tests.
Following new config options are added:
`skip_scenario_tests` - Skip all scenario tests
`skip_functional_tests` - Skip all functional tests
`skip_functional_test_list` - List of functional tests to skip
`skip_scenario_test_list` - List of scenario tests to skip
`skip_test_stack_action_list` - List of actions in tests to skip
Change-Id: I7a5233f5db1f065ccee5a97408c72203c108a656
Depends-On: I25c5e853f0499b88f2803b077d19e132140908f1
Currently this is only done if you override a python resource
and not if you override a template resource.
Closes-bug: #1479565
Change-Id: I29f65d5058c8c2e8b04cb1fcbcb4956040ec908a
Add functional test that executes the following scenario:
- suspend a stack with template resource
- resume a stack with template resource.
Change-Id: I7e1ff7785f48d861752d681d26866c985b8c8513
Closes-bug: #1479595
In _stack_output() look for unexpected "output_error" messages.
Fix a missing output in the template resource tests.
Change-Id: I71d5d7e5800d7503d9e6015f637fe7fef5d867fe
This produces a nested exception like:
'ValueError: resources.nested.resources.my_server: it is broken, sorry'
This re-uses the path mechanism that StackValidationFailed exception
uses.
Change-Id: Id5204c15ee96784e04522ab3c5a8e66900f9a1d3
Closes-bug: 1459837
This fix adds schema regeneration before props are validated
for TemplateResource during stack-update.
Change-Id: Ia79a25083489f48ed7332fbbd089a0090452cdc4
Closes-Bug: #1452983
Closes-Bug: #1453923
The main methods create/update/delete in HeatIntegrationTest class
already contains _wait_for_stack_status, so we can remove duplicate
checks in tests.
Also was added paramter enable_cleanup for stack_create method, which
allows to disable CleanUp method in tests, where we delete stack
manually.
Change-Id: I41b546d648656676ec9bc3b38940eac68f9a848d
We are persisting for a number of reasons:
- so we don't have to pass this through ever rpc call
- the API exposes parent_resource (currently always None as
it is not persisted)
Closes-bug: #1438978
Change-Id: Id2db36c0234a085ec4f0ce2ab114ec483ea29d81
Later the integration jobs can be tuned to have their own
logging settings.
This change also raises _log_console_output to info, so it is displayed
by default.
Change-Id: Ifcaa6faf76c655e0c8cfd7d76775b80de70062c4
This tries to prove that if you manually delete a nested
stack, the parent stack is still deletable.
part of blueprint decouple-nested
Change-Id: I1d0bf7b5d982dc1f312fbe70cbb09a2e624e3371
In the case of a dependant resource failing, a nested stack will not get
created, so we need to at least create an empty nested stack to allow
the update to work.
Change-Id: I2e83546801bce0da566ec8ef1322e30d695ff02a
Closes-bug: 1411103
Note: this enables adopt and abandon in the gate
so we can test this feature.
Part of blueprint decouple-nested
Change-Id: Id1e63fc4b4e609f699d718b8569c25d246e83faa
