vagrant provisioning fails with ansible 2

RESOLVED FIXED

Status

developer.mozilla.org
General
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: willkg, Assigned: willkg)

Tracking

Details

If you install ansible 2 and then try to create a new vm, vagrant provisioning fails with:

TASK [Mayeu.RabbitMQ : add the official rabbitmq repository] *******************
fatal: [developer-local]: FAILED! => {"changed": false, "failed": true, "msg": "could not find src=/home/willkg/mozilla/files/rabbitmq.list"}

If I downgrade to ansible <2, then everything works fine.

This bug covers fixing that and whatever else is broken with ansible 2.
I think it's this task in provisioning/roles/Mayeu.RabbitMQ/tasks/install/main.yml:

- 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


That's a relative path. rabbitmq.list exists in files/, so I think this should just get fixed to rabbitmq.list.

Grabbing this to fix and test with ansible 1.9 and 2.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
In a PR: https://github.com/mozilla/kuma/pull/3764

That works with both ansible 1.9 and 2. It's based on the changes in this PR:

https://github.com/Mayeu/ansible-playbook-rabbitmq/pull/56

Comment 3

2 years ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/6f044eacfa5f67607c5b0ebf1dd7b05a0f7fef8d
Fix bug 1241554: Fixes rabbitmq task to work with ansible 2

This tweaks bits of the rabbitmq task using the changes in this PR:

https://github.com/Mayeu/ansible-playbook-rabbitmq/pull/56/

That allows the task to work with both ansible 1.9 and 2.

https://github.com/mozilla/kuma/commit/42d5ce279c14610e43bf27db33923610342e342a
Merge pull request #3764 from mozilla/1241554-ansible

Fix bug 1241554: Fixes rabbitmq task to work with ansible 2

Updated

2 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.