88a20e7a20
1. The test did "name: '{{hostnames}}.{{item}}'" inside a with_sequence
loop, which didn't do what was intended: it expanded hostnames into
an array, appended ".1", and set name to the resulting string. This
can be converted to a simple with_items loop.
2. Some of the entries in hostnames contained punctuation characters,
which I see no reason to support in inventory hostnames anyway.
3. Once the add_host failures are fixed, the playbook later fails when
the unicode hostnames are interpolated into debug output in ssh.py
due to an encoding error. This is only one of the many places that
may fail when using unicode inventory hostnames; we work around it
by providing an ansible_ssh_host setting.
|
9 years ago | |
|---|---|---|
| .. | ||
| group_vars | 11 years ago | |
| host_vars | 11 years ago | |
| lookup_paths | 9 years ago | |
| roles | 9 years ago | |
| vars | 9 years ago | |
| Makefile | 9 years ago | |
| README.md | 11 years ago | |
| all.yml | 10 years ago | |
| amazon.yml | 10 years ago | |
| azure.yml | 10 years ago | |
| bad_parsing.yml | 10 years ago | |
| check_mode.yml | 10 years ago | |
| cleanup_azure.py | 10 years ago | |
| cleanup_ec2.py | 9 years ago | |
| cleanup_gce.py | 9 years ago | |
| cleanup_rax.py | 9 years ago | |
| cloudstack.yml | 9 years ago | |
| consul.yml | 10 years ago | |
| consul_inventory.yml | 10 years ago | |
| consul_running.py | 9 years ago | |
| credentials.template | 9 years ago | |
| destructive.yml | 10 years ago | |
| galaxy_playbook.yml | 10 years ago | |
| galaxy_roles.yml | 9 years ago | |
| galaxy_rolesfile | 10 years ago | |
| gce.yml | 11 years ago | |
| gce_credentials.py | 11 years ago | |
| good_parsing.yml | 10 years ago | |
| integration_config.yml | 9 years ago | |
| inventory | 10 years ago | |
| inventory.group_by | 11 years ago | |
| inventory.handlers | 11 years ago | |
| inventory.winrm.template | 11 years ago | |
| lookup.ini | 9 years ago | |
| lookup.properties | 10 years ago | |
| non_destructive.yml | 9 years ago | |
| rackspace.yml | 10 years ago | |
| setup_gce.py | 9 years ago | |
| test_delegate_to.yml | 10 years ago | |
| test_environment.yml | 9 years ago | |
| test_filters.yml | 10 years ago | |
| test_force_handlers.yml | 9 years ago | |
| test_group_by.yml | 9 years ago | |
| test_handlers.yml | 9 years ago | |
| test_hash.yml | 11 years ago | |
| test_includes.yml | 10 years ago | |
| test_includes2.yml | 9 years ago | |
| test_lookup_properties.yml | 9 years ago | |
| test_setup.yml | 11 years ago | |
| test_tags.yml | 10 years ago | |
| test_templating_settings.yml | 10 years ago | |
| test_var_precedence.yml | 9 years ago | |
| test_vault.yml | 11 years ago | |
| test_winrm.yml | 10 years ago | |
| unicode.yml | 9 years ago | |
| vars_file.yml | 10 years ago | |
| vault-password | 11 years ago | |
README.md
Integration tests
The ansible integration system.
Tests for playbooks, by playbooks.
Some tests may require credentials. Credentials may be specified with credentials.yml.
Tests should be run as root.
Configuration
Making your own version of integration_config.yml can allow for setting some
tunable parameters to help run the tests better in your environment. Some
tests (e.g. cloud) will only run when access credentials are provided. For
more information about supported credentials, refer to credentials.template.
Prerequisites
The tests will assume things like hg, svn, and git are installed and in path.
(Complete list pending)
Non-destructive Tests
These tests will modify files in subdirectories, but will not do things that install or remove packages or things outside of those test subdirectories. They will also not reconfigure or bounce system services.
Run as follows:
make non_destructive
You can select specific tests with the --tags parameter.
TEST_FLAGS="--tags test_vars_blending" make
Destructive Tests
These tests are allowed to install and remove some trivial packages. You will likely want to devote these to a virtual environment. They won't reformat your filesystem, however :)
make destructive
Cloud Tests
Cloud tests exercise capabilities of cloud modules (e.g. ec2_key). These are not 'tests run in the cloud' so much as tests that leverage the cloud modules and are organized by cloud provider.
In order to run cloud tests, you must provide access credentials in a file
named credentials.yml. A sample credentials file named
credentials.template is available for syntax help.
Provide cloud credentials: cp credentials.template credentials.yml ${EDITOR:-vi} credentials.yml
Run the tests: make cloud
WARNING running cloud integration tests will create and destroy cloud resources. Running these tests may result in additional fees associated with your cloud account. Care is taken to ensure that created resources are removed. However, it is advisable to inspect your AWS console to ensure no unexpected resources are running.
Windows Tests
These tests exercise the winrm connection plugin and Windows modules. You'll need to define an inventory with a remote Windows 2008 or 2012 Server to use for testing, and enable PowerShell Remoting to continue.
Running these tests may result in changes to your Windows host, so don't run them against a production/critical Windows environment.
Enable PowerShell Remoting (run on the Windows host via Remote Desktop): Enable-PSRemoting -Force
Define Windows inventory: cp inventory.winrm.template inventory.winrm ${EDITOR:-vi} inventory.winrm
Run the tests: make test_winrm