|
| 1 | +#/usr/bin/env bats |
| 2 | + |
| 3 | +# This test file is for testing ansible-runner on a production appliance to verify |
| 4 | +# that the real installation is working as expected. It is a duplicate of the tests |
| 5 | +# in runner_execution_spec.rb but without the rspec and rspec-rails overhead. |
| 6 | +# |
| 7 | +# This test requires the Bats test framework to be installed |
| 8 | +# macOS: brew install bats-core |
| 9 | +# appliance: dnf install bats |
| 10 | +# as well as the bats-support and bats-assert plugins installed |
| 11 | +# git clone https://github.com/bats-core/bats-support ~/.bats/libs/bats-support |
| 12 | +# git clone https://github.com/bats-core/bats-assert ~/.bats/libs/bats-assert |
| 13 | + |
| 14 | +setup_file() { |
| 15 | + export BATS_LIB_PATH="$HOME/.bats/libs:$BATS_LIB_PATH" |
| 16 | + |
| 17 | + export PYTHON_VERSION="3.12" |
| 18 | + |
| 19 | + export SCRIPT_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")" >/dev/null 2>&1 && pwd)" |
| 20 | + export DATA_DIR="$SCRIPT_DIR/runner/data" |
| 21 | + export TEST_DIR="/tmp/ansible-runner-test" |
| 22 | + export ROLES_DIR="/tmp/ansible-runner-test-roles" |
| 23 | + export VAULT_FILE="$TEST_DIR/vault_password" |
| 24 | +} |
| 25 | + |
| 26 | +setup() { |
| 27 | + bats_load_library 'bats-support' |
| 28 | + bats_load_library 'bats-assert' |
| 29 | + |
| 30 | + rm -rf $TEST_DIR |
| 31 | + rm -rf $ROLES_DIR |
| 32 | + |
| 33 | + mkdir -p $TEST_DIR |
| 34 | +} |
| 35 | + |
| 36 | +teardown() { |
| 37 | + rm -rf $DATA_DIR/hello_world_with_requirements_github/roles/manageiq.example |
| 38 | +} |
| 39 | + |
| 40 | +setup_roles_dir() { |
| 41 | + # In prod builds, ansible-galaxy lives in the venv, so set up the PATH temporarily to install the roles |
| 42 | + PATH="/var/lib/manageiq/venv/bin:$PATH" |
| 43 | + |
| 44 | + roles_path="$1" |
| 45 | + source_role_file="${2:-$1/requirements.yml}" |
| 46 | + role_file="$roles_path/requirements.yml" |
| 47 | + if [ "$source_role_file" != "$role_file" ]; then |
| 48 | + mkdir -p $roles_path |
| 49 | + cp $source_role_file $role_file |
| 50 | + fi |
| 51 | + ansible-galaxy install --roles-path=$roles_path --role-file=$role_file |
| 52 | + |
| 53 | + PATH="${PATH#*:}" |
| 54 | +} |
| 55 | + |
| 56 | +################################################################################ |
| 57 | + |
| 58 | +exec_ansible_runner_cli() { |
| 59 | + PATH="/var/lib/manageiq/venv/bin:$PATH" \ |
| 60 | + PYTHONPATH="/var/lib/manageiq/venv/lib/python${PYTHON_VERSION}/site-packages:/usr/local/lib64/python${PYTHON_VERSION}/site-packages:/usr/local/lib/python${PYTHON_VERSION}/site-packages:/usr/lib64/python${PYTHON_VERSION}/site-packages:/usr/lib/python${PYTHON_VERSION}/site-packages" \ |
| 61 | + ansible-runner run $TEST_DIR --ident result --playbook $1 --project-dir $DATA_DIR |
| 62 | +} |
| 63 | + |
| 64 | +exec_ansible_runner_cli_role() { |
| 65 | + PATH="/var/lib/manageiq/venv/bin:$PATH" \ |
| 66 | + PYTHONPATH="/var/lib/manageiq/venv/lib/python${PYTHON_VERSION}/site-packages:/usr/local/lib64/python${PYTHON_VERSION}/site-packages:/usr/local/lib/python${PYTHON_VERSION}/site-packages:/usr/lib64/python${PYTHON_VERSION}/site-packages:/usr/lib/python${PYTHON_VERSION}/site-packages" \ |
| 67 | + ansible-runner run $TEST_DIR --ident result --role $1 --roles-path $ROLES_DIR --role-skip-facts --hosts localhost |
| 68 | +} |
| 69 | + |
| 70 | +@test "[ansible-runner] runs a playbook" { |
| 71 | + run exec_ansible_runner_cli hello_world.yml |
| 72 | + assert_success |
| 73 | + assert_output --partial '"msg": "Hello World!"' |
| 74 | +} |
| 75 | + |
| 76 | +@test "[ansible-runner] runs a playbook with variables in a vars file" { |
| 77 | + # run ansible-runner run $TEST_DIR --ident result --playbook hello_world_vars_file.yml --project-dir $DATA_DIR |
| 78 | + run exec_ansible_runner_cli hello_world_vars_file.yml |
| 79 | + assert_success |
| 80 | + assert_output --partial '"msg": "Hello World! vars_file_1=vars_file_1_value, vars_file_2=vars_file_2_value"' |
| 81 | +} |
| 82 | + |
| 83 | +@test "[ansible-runner] runs a playbook with vault encrypted variables" { |
| 84 | + echo -n "vault" >> $VAULT_FILE |
| 85 | + ANSIBLE_VAULT_PASSWORD_FILE=$VAULT_FILE run exec_ansible_runner_cli hello_world_vault_encrypted_vars.yml |
| 86 | + assert_success |
| 87 | + assert_output --partial '"msg": "Hello World! (NOTE: This message has been encrypted with ansible-vault)"' |
| 88 | +} |
| 89 | + |
| 90 | +@test "[ansible-runner] runs a playbook with variables in a vault encrypted vars file" { |
| 91 | + echo -n "vault" >> $VAULT_FILE |
| 92 | + ANSIBLE_VAULT_PASSWORD_FILE=$VAULT_FILE run exec_ansible_runner_cli hello_world_vault_encrypted_vars_file.yml |
| 93 | + assert_success |
| 94 | + assert_output --partial '"msg": "Hello World! vars_file_1=vars_file_1_value, vars_file_2=vars_file_2_value"' |
| 95 | +} |
| 96 | + |
| 97 | +@test "[ansible-runner] runs a playbook using roles from github" { |
| 98 | + setup_roles_dir $DATA_DIR/hello_world_with_requirements_github/roles |
| 99 | + |
| 100 | + run exec_ansible_runner_cli hello_world_with_requirements_github/hello_world_with_requirements_github.yml |
| 101 | + assert_success |
| 102 | + assert_output --partial '"msg": "Hello World! example_var='\''example var value'\''"' |
| 103 | +} |
| 104 | + |
| 105 | +@test "[ansible-runner] runs a role" { |
| 106 | + setup_roles_dir $ROLES_DIR $DATA_DIR/hello_world_with_requirements_github/roles/requirements.yml |
| 107 | + |
| 108 | + run exec_ansible_runner_cli_role manageiq.example |
| 109 | + assert_success |
| 110 | + assert_output --partial '"msg": "Hello from manageiq.example role! example_var='\''example var value'\''"' |
| 111 | +} |
| 112 | + |
| 113 | +@test "[ansible-runner] vmware collection" { |
| 114 | + if [ ! -d /var/lib/manageiq/venv ]; then |
| 115 | + skip "manageiq venv collections are not present" |
| 116 | + fi |
| 117 | + |
| 118 | + run exec_ansible_runner_cli vmware.yml |
| 119 | + assert_failure # We expect to this to fail due to connecting to an unknown vcenter |
| 120 | + assert_output --partial '"msg": "Unknown error while connecting to vCenter or ESXi API at vcenter_hostname:443 : [Errno -2] Name or service not known"' |
| 121 | +} |
| 122 | + |
| 123 | +@test "[ansible-runner] aws collection" { |
| 124 | + if [ ! -d /var/lib/manageiq/venv ]; then |
| 125 | + skip "manageiq venv collections are not present" |
| 126 | + fi |
| 127 | + |
| 128 | + run exec_ansible_runner_cli aws.yml |
| 129 | + assert_failure # We expect to this to fail due to connecting with bad creds |
| 130 | + assert_output --partial '"msg": "Failed to describe instances: An error occurred (AuthFailure) when calling the DescribeInstances operation: AWS was not able to validate the provided access credentials"' |
| 131 | +} |
| 132 | + |
| 133 | +################################################################################ |
| 134 | + |
| 135 | +exec_ansible_runner() { |
| 136 | + rails runner "resp = Ansible::Runner.run({}, {}, '$DATA_DIR/$1'); puts resp.human_stdout; exit resp.return_code" |
| 137 | +} |
| 138 | + |
| 139 | +exec_ansible_runner_role() { |
| 140 | + rails runner "resp = Ansible::Runner.run_role({}, {}, '$1', roles_path: '$ROLES_DIR'); puts resp.human_stdout; exit resp.return_code" |
| 141 | +} |
| 142 | + |
| 143 | +@test "[Ansible::Runner] runs a playbook" { |
| 144 | + run exec_ansible_runner hello_world.yml |
| 145 | + assert_success |
| 146 | + assert_output --partial '"msg": "Hello World!"' |
| 147 | +} |
| 148 | + |
| 149 | +@test "[Ansible::Runner] runs a playbook with variables in a vars file" { |
| 150 | + run exec_ansible_runner hello_world_vars_file.yml |
| 151 | + assert_success |
| 152 | + assert_output --partial '"msg": "Hello World! vars_file_1=vars_file_1_value, vars_file_2=vars_file_2_value"' |
| 153 | +} |
| 154 | + |
| 155 | +@test "[Ansible::Runner] runs a playbook with vault encrypted variables" { |
| 156 | + skip "requires database access" |
| 157 | + |
| 158 | + run exec_ansible_runner hello_world_vault_encrypted_vars.yml |
| 159 | + assert_success |
| 160 | + assert_output --partial '"msg": "Hello World! (NOTE: This message has been encrypted with ansible-vault)"' |
| 161 | +} |
| 162 | + |
| 163 | +@test "[Ansible::Runner] runs a playbook with variables in a vault encrypted vars file" { |
| 164 | + skip "requires database access" |
| 165 | + |
| 166 | + run exec_ansible_runner hello_world_vault_encrypted_vars_file.yml |
| 167 | + assert_success |
| 168 | + assert_output --partial '"msg": "Hello World! vars_file_1=vars_file_1_value, vars_file_2=vars_file_2_value"' |
| 169 | +} |
| 170 | + |
| 171 | +@test "[Ansible::Runner] runs a playbook using roles from github" { |
| 172 | + run exec_ansible_runner hello_world_with_requirements_github/hello_world_with_requirements_github.yml |
| 173 | + assert_success |
| 174 | + assert_output --partial '"msg": "Hello World! example_var='\''example var value'\''"' |
| 175 | +} |
| 176 | + |
| 177 | +@test "[Ansible::Runner] runs a role" { |
| 178 | + setup_roles_dir $ROLES_DIR $DATA_DIR/hello_world_with_requirements_github/roles/requirements.yml |
| 179 | + |
| 180 | + run exec_ansible_runner_role manageiq.example |
| 181 | + assert_success |
| 182 | + assert_output --partial '"msg": "Hello from manageiq.example role! example_var='\''example var value'\''"' |
| 183 | +} |
| 184 | + |
| 185 | +@test "[Ansible::Runner] vmware collection" { |
| 186 | + if [ ! -d /var/lib/manageiq/venv ]; then |
| 187 | + skip "manageiq venv collections are not present" |
| 188 | + fi |
| 189 | + |
| 190 | + run exec_ansible_runner vmware.yml |
| 191 | + assert_failure # We expect to this to fail due to connecting to an unknown vcenter |
| 192 | + assert_output --partial '"msg": "Unknown error while connecting to vCenter or ESXi API at vcenter_hostname:443 : [Errno -2] Name or service not known"' |
| 193 | +} |
| 194 | + |
| 195 | +@test "[Ansible::Runner] aws collection" { |
| 196 | + if [ ! -d /var/lib/manageiq/venv ]; then |
| 197 | + skip "manageiq venv collections are not present" |
| 198 | + fi |
| 199 | + |
| 200 | + run exec_ansible_runner aws.yml |
| 201 | + assert_failure # We expect to this to fail due to connecting with bad creds |
| 202 | + assert_output --partial '"msg": "Failed to describe instances: An error occurred (AuthFailure) when calling the DescribeInstances operation: AWS was not able to validate the provided access credentials"' |
| 203 | +} |
0 commit comments