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
This test does not wait, when all resources will be created. However,
it does not mean, that these resources will not be in create in
progress state. The error, mentioned in the bug, happens, when nova
tries to create server and see two available networks (private and
heat-net). Current patch prevents error by adding network
property to Server resource.
Change-Id: I7c1f4931976ae3a899563b1a9da9f8bc7564806c
Closes-Bug: #1467529
for integration tests. Use a flavor similar to m1.micro for that.
It is enough to start both minimal and functional tests images with no
serious payload and should decrease the amount of RAM consumed by VMs
in corresponding tests four-fold.
Change-Id: I378b5a3cde020176ac45ebf8d05bd13278861a4e
Related-Bug: #1435285
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
When doing the initial validate(), skip validating values by setting
the stack strict_validate to False, otherwise we incorrectly fail
validation when values are passed in via properties/parameters which
refer to resources in the parent stack.
Co-Authored-by: Angus Salkeld <asalkeld@mirantis.com>
Change-Id: Ib75c2de6c32373de72901b9f7c5e3828bd9ee7d9
Closes-Bug: #1407100
Closes-Bug: #1407877
Closes-Bug: #1405446
