anazobec
commented
1 year ago Hi, it is possible to view a more detailed error log from ansible using the ansible_playbook_stderr and ansible_playbook_stdout variables (here). You can view them by either adding an output block with those variables or viewing the state file terraform.tfstate which is created upon terraform apply. It is possible that the state file won't contain any details about this resource since it has failed to be created due to an error, but by using ignore_playbook_errors = true and (if needed) adding ansible_check_mode = true to extra_vars, the resource will be created regardless of the error (from running the playbook). So, your terraform script (the one you provided here) would look something like this.
terraform {
required_version = "~> 1.5.0"
required_providers {
ansible = {
version = "~> 1.1.0"
source = "ansible/ansible"
}
}
}
resource "ansible_playbook" "default" {
playbook = "playbooks/configure_default.yml"
name = "xyz-dev-default-362a135c"
extra_vars = {
ansible_host = "1.2.3.4"
private_key = sensitive("123456")
ansible_ssh_user = "root"
ansible_check_mode = true # <- here
}
verbosity = 1
ignore_playbook_failure = true # <- here
}
## You may skip the below blocks and view the terraform.tfstate instead ##
# output stderr
output "playbook_stderr" {
value = ansible_playbook.default.ansible_playbook_stderr
}
# output stdout
output "playbook_stdout" {
value = ansible_playbook.default.ansible_playbook_stdout
}Taking a more detailed look at the code you've provided, I think your error could be resolved by making name and ansible_host the same value. Variable name is a hostname provided for the creation of the temporary inventory file (the kind you've found left over from failed run), so maybe either changing the value of name to the value of ansible_host or the other way around (depending on your needs) may resolve this issue. To give a more detailed explanation... ansible_host (from your example) is set to 1.2.3.4, but the name is set to xyz-dev-default-362a135c. So the temporary inventory file would look something like this:
[default]
xyz-dev-default-362a135cUpon executing the terraform apply, the playbook (using this temp inventory file) searches for the provided ansible_host which is set to 1.2.3.4, but since it doesn't exist in that inventory, the resource fails to create (the playbook fails).
Hope this helps :)
lae
rwblokzijl
kdpuvvadi
smtarslanturk
kgopi1
gravesm
multinegsix
When
ansible-playbooket al fail, its output does not seem to be captured and provided to Terraform (or maybe it is but it crashes), which leads to confusion and troubleshooting that should be unnecessary. The debug output includesThere may be an error within your playbook.as a way of informing the user, I'm sure, but this is very vague and really not that helpful during development. I'm not sure if this is a bug or it's not implemented, but this information should be provided to the user so they know what to fix.32 and #20 (#16) are symptoms of this issue and probably wouldn't have been opened if CLI output from the Ansible tooling was appropriately sent up the chain to Terraform, as far as I can tell.
Anyway, the following was one of my reproductions of the plugin crashing whenever
ansible-playbookerrored out, for whatever reason (inventory issues were masked by this as well).playbook.tfplaybooks/configure_default.yml:TF_LOG=debug terraform applyansible-playbook -v -e hostname=xyz-dev-default-362a135c -e ansible_host=1.2.3.4 -e ansible_ssh_user=root -e private_key=123456 playbooks/configure_default.yml -i /tmp/.inventory-253854049.ini(inventory file left over from failed run)