tripleo-common/tripleo_common/tests/actions
Emilien Macchi c9adf14a21 ansible: limit_hosts now takes precedence over blacklisted_hostnames
From now, limit_hosts will take precedence over the blacklisted_hostnames.
And therefore Ansible won't be run with two --limit if both limit hosts
and blacklisted hostnames are in use. When we want to run Ansible on
specific hosts, we will ignore the blacklisted nodes and assume we know
what we do. In the case of the scale-down scenario, the unreachable nodes
are ignored.

Note: adding unit tests coverage for both parameters.

Change-Id: I2e9fc7b9e9005fce7d956f1b936054e540b39849
Closes-Bug: #1857298
(cherry picked from commit 76bc13e3bf)
2020-07-15 17:56:28 -04:00
..
__init__.py Initial Integration of Mistral into TripleO 2016-05-16 09:15:14 -04:00
test_ansible.py ansible: limit_hosts now takes precedence over blacklisted_hostnames 2020-07-15 17:56:28 -04:00
test_baremetal.py Use unittest.mock instead of third party mock 2020-05-15 18:58:43 +02:00
test_base.py Use unittest.mock instead of third party mock 2020-05-15 18:58:43 +02:00
test_derive_params.py Use unittest.mock instead of third party mock 2020-05-15 18:58:43 +02:00
test_parameters.py Use unittest.mock instead of third party mock 2020-05-15 18:58:43 +02:00
test_plan.py Use unittest.mock instead of third party mock 2020-05-15 18:58:43 +02:00
test_scale.py Use unittest.mock instead of third party mock 2020-05-15 18:58:43 +02:00
test_validations.py Use unittest.mock instead of third party mock 2020-05-15 18:58:43 +02:00