"TASK Mayeu.RabbitMQ : add the official rabbitmq repository" fails for vmware-iso and

[packet-rat]

Investigating:

Initial "$ packer build stucco.json":

vmware-iso: TASK [Mayeu.RabbitMQ : add the official rabbitmq repository] ******************* vmware-iso: task path: /tmp/packer-provisioner-ansible-local/roles/Mayeu.RabbitMQ/tasks/install/debian.yml:8 vmware-iso: fatal: [stucco]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"backup": "yes", "dest": "/etc/apt/sources.list.d/", "src": "../../files/rabbitmq.list"}, "module_name": "copy"}, "msg": "could not find src=/files/rabbitmq.list"} vmware-iso: to retry, use: --limit @/tmp/packer-provisioner-ansible-local/site.retry

virtualbox-iso: TASK [Mayeu.RabbitMQ : add the official rabbitmq repository] ******************* virtualbox-iso: task path: /tmp/packer-provisioner-ansible-local/roles/Mayeu.RabbitMQ/tasks/install/debian.yml:8 virtualbox-iso: fatal: [stucco]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"backup": "yes", "dest": "/etc/apt/sources.list.d/", "src": "../../files/rabbitmq.list"}, "module_name": "copy"}, "msg": "could not find src=/files/rabbitmq.list"} virtualbox-iso: to retry, use: --limit @/tmp/packer-provisioner-ansible-local/site.retry

[packet-rat]

Cleared this "TASK [Mayeu.RabbitMQ : add the official rabbitmq repository]" error by editing:
/demo-master/provisioning/roles/Mayeu.RabbitMQ/tasks/install/debian.yml':

Changing Line 10:

From: "src=../../files/rabbitmq.list"
To: "src=roles/Mayeu.RabbitMQ/files/rabbitmq.list"

- name: add the official rabbitmq repository
  copy:
    src=../../files/rabbitmq.list
    dest=/etc/apt/sources.list.d/
    backup=yes
  register: aptrepo
  when: not rabbitmq_os_package

- name: add the official rabbitmq repository
  copy:
    src=roles/Mayeu.RabbitMQ/files/rabbitmq.list
    dest=/etc/apt/sources.list.d/
    backup=yes
  register: aptrepo
  when: not rabbitmq_os_package

[mikeiannacone]

That's strange. The role itself hasn't changed upstream, but I can reproduce this problem, and your change did fix it. And yet I'm almost positive this worked in the past. Maybe ansible's behavior changed at some point? I'm on 2.0.1.0 currently - maybe I should just specify that as the minimum ansible version in the readme?

Either way, I added this change in 470bc42

[mikeiannacone]

hm, looks like this is actually a known issue with this role under ansible 2.

Mayeu/ansible-playbook-rabbitmq#56
Mayeu/ansible-playbook-rabbitmq#57

I'll re-test with their updated version once it's available.

Thanks for the heads up and the fix for this @packet-rat