I have a playbook that has a reboot directive at the end, with a pause and prompt at the end to allow me to interrupt and abort the playbook without rebooting. Or at least, it used to.
I pointed the playbook at ~28 machines. Twice yesterday, it rebooted half the machines even though the play had paused and I cancelled it with Ctrl+c and then Shift+a. Each time I ran the playbook, half or more of the hosts proceeded on to the next step and rebooted in spite of the interrupt. When I test on localhost now (only one host), the interrupt works just fine with 'a' or 'A'. Can this be caused by my parallelization being too high for my control host? ansible version: Ansible 2.1.0 The command line prompt for abort states to use "A" to abort, which is why I used shift+a. Press 'C' to continue the play or 'A' to abort >From the docs <http://docs.ansible.com/ansible/pause_module.html>: To abort a playbook: press ctrl+c and thena. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/bf5e0946-0368-48cc-a7f6-d5ac3e90e20d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
