This issue was originally opened by @JKetelaar as hashicorp/packer#10477. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
Overview of the Issue
Whenever I am creating a parallel build, the Ansible provisioner uses only one build entity, in each of the tasks.
Reproduction Steps
Run Packer with an Ansible provisioner and two builders.
It will run the provisioner on only one builder.
As you can see in the log output on line 5 and line 7 it shows two different IPs (116.203.213.239 and 116.203.51.13).
If you then look on line 28, it shows that the gocd builder indeed has the right IP (116.203.213.239), though looking at line 67 it shows that also the common builder uses the gocd builder IP address.
This issue was originally opened by @JKetelaar as hashicorp/packer#10477. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
Overview of the Issue
Whenever I am creating a parallel build, the Ansible provisioner uses only one build entity, in each of the tasks.
Reproduction Steps
Run Packer with an Ansible provisioner and two builders. It will run the provisioner on only one builder.
Packer version
Simplified Packer Buildfile
Build file
Ansible playbook (
./playbooks/packer-debug.yml
)As you can see in the log output on line 5 and line 7 it shows two different IPs (
116.203.213.239
and116.203.51.13
). If you then look on line 28, it shows that the gocd builder indeed has the right IP (116.203.213.239
), though looking at line 67 it shows that also the common builder uses the gocd builder IP address.Operating system and Environment details
Both on Ubuntu 20 and MacOS.
Log Fragments and crash.log files
https://gist.github.com/JKetelaar/6cfab554d0f24f0b4f1b653c82aadf84