Multiple builders with Ansible galaxy roles race about packer-plugin-ansible HOT 3 OPEN

Of note, this is particularly problematic and reproducible when using galaxy_force_install = true

from packer-plugin-ansible.

Ugh, I started hitting this too when I made some changes to the project that caused my vsphere-clone and virtualbox-ovf builders to provision around the same time. Perhaps I'll stick in a "sleep" provisioner to delay one of the builders, like this:

provisioner "shell" {
    only = ["vsphere-clone.dev-env"]
    inline_shebang = "/bin/bash -l"
    inline = [
      "echo Delaying the vSphere provisioner a bit to prevent ansible-galaxy collisions.",
      "echo This is a workaround for https://github.com/hashicorp/packer-plugin-ansible/issues/21...",
      "sleep 30"
    ]
  }

Assuming packer builder environments do NOT provide any sort of separation of ansible workspaces, it would seem that another workaround would be to separate the provisioners for each builder using only/except, and for each provide a different roles path and collections_path. In theory, this would inform the separate ansible processes (spawned by separate packer builder processes) to install roles and collections from ansible-galaxy into distinct folders. (It also tells the ansible processes where to look for roles/collections at runtime..)

Seems like that would work, but man what a mess to have to implement as a workaround. I'm all ears if someone else has ideas.

from packer-plugin-ansible.

Yeah, I still have this issue. It tries to (forceably) install a role that is in use by another build. Omitting the galaxy_force will result in errors about a role already being present. I've solved this by adding the roles to the actual repository and not using ansible galaxy to install them

from packer-plugin-ansible.