Running ansible-playbook -vvv migration.yml locally on the server (in tmux), I noticed:
the migration will run regardless of the existence of dovecot.index.log
it will continue running the background if you ^C it, and the only safe way I could figure of killing it was to first systemctl stop dovecot, then kill -9 the dsync processes, restart dovecot, comment out the creates: thing (since it wasn't doing anything anyway), and restart the sync process.
We need to:
Figure out why creates: is being ignored
Make sure that when the user ^C's the dsync, it actually stops the sync.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5853538-migration-step-ignores-ansible-s-creates-argument-proceeds-anyway?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github).
Running
ansible-playbook -vvv migration.ymllocally on the server (in tmux), I noticed:dovecot.index.log^Cit, and the only safe way I could figure of killing it was to firstsystemctl stop dovecot, thenkill -9thedsyncprocesses, restart dovecot, comment out thecreates:thing (since it wasn't doing anything anyway), and restart the sync process.We need to:
creates:is being ignored^C's thedsync, it actually stops the sync.