Confirmed the second issue. Here's a small playbook that shows the problems:

---
# Localhost is a fedora box
- hosts: rhel6-test
  vars:
    device_host: rhel6-test
    top_dir: /var/tmp
  tasks:
    - name: Push fedora file to rhel host
      synchronize:
        src: "/etc/redhat-release"
        dest: "/var/tmp/fedora-rel"
        mode: push
    - name: Pull redhat file to fedora host
      synchronize:
        src: "/etc/redhat-release"
        dest: "/var/tmp/redhat-rel"
        mode: pull

In current devel, both of those plays are copying the remote /etc/redhat-release file to a file on the remote machine. So the remote machine ends up with /var/tmp/fedora-rel and /var/tmp/redhat-rel and both of those are the /etc/redhat-release from the rhel6 box, not the one from the fedora box that ansible-playbook is being run from.

Yes, the first issue and the second are actually related, since it tries to sync two folders on remote, and I do not have any ssh info on the remote, when src tries to go to ubuntu@ip:dest, it fails, and gives me permission denied error.

I also tried to setup my ssh info on the remote server, and then it succeeded. Therefore, that is the issue.

Small update on my debugging of this -- in 1.9.x the tasks run the ansible module (not just the action plugin) on the controller rather than the remote host. In 2.0 it's running the ansible module on the remote host. Will need to see what is happening with delegate_to to determine if there's a reason that the ansible module exists and try to find the specialcase code in 1.9 that handles this.

This works if delegate_to: localhost is explicitly stated. jimi-c's theory is that in v2 we've already built the connection by the time the synchronize action plugin's run() method is called. So all of the fancy stuff it tries to do to modify how the connection is setup isn't having an effect. Will try to have the synchronize action plugin create its own connection object and use that instead.

delegating to $other host instead of localhost is also working. That would seem to validate jimi-c's theory.

Alright everyone, that PR makes syynchronize work at least for these basic cases for me. Feel free to let us know if you notice additional regressions.

Closing This Ticket

Hi!

We believe recent commits (likely detailed above) should resolve this question or problem for you.

This will also be included in the next major release.

If you continue seeing any problems related to this issue, or if you have any further questions, please let us know by stopping by one of the two mailing lists, as appropriate:

• https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
• https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code

Because this project is very active, we're unlikely to see comments made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular
issue is resolved.

Thank you!