Ansible pause module fails to abort when more than one host is in inventory list

[binbash root]

Originally opened bug #14252 but this bug  for Ansible 2.0.0.1, but this still appears to be in Ansible 2.0.1.0.   It doesn't matter whether the first host is remote or local connection.  The first host will fail but subsequent hosts will still attempt the next task instead of aborting.  Wasn't sure if I should file another bug on this or not.

 

Ansible host:  RHEL6

Ansible version 2.0.1.0  (pip installation)

Ansible Clients RHEL l5/6

 

 

inventoryfile:

[alpha]
piansiapst01 ansible_connection=local
dgitapp01
alexandria

 

playbook

---
- hosts: alpha
  gather_facts: True
  become: True
  tasks:
    - name: foo test
      pause: prompt="Proving that ctrl-c-a doesn't work"

    - debug:  msg="See what I mean"

 

 

Output:

[root@piansiapst01 ansible]# ansible-playbook -i testLinux testpause.yaml -k -u foouser
SSH password:

 

PLAY ***************************************************************************

TASK [setup] *******************************************************************
ok: [piansiapst01]
ok: [alexandria]
ok: [dgitapp01]

TASK [foo test] ****************************************************************
[foo test]
Proving that ctrl-c-a doesn't work:
Press 'C' to continue the play or 'A' to abort
fatal: [piansiapst01]: FAILED! => {"failed": true, "msg": "user requested abort!"}

TASK [debug] *******************************************************************
ok: [dgitapp01] => {
    "msg": "See what I mean"
}
ok: [alexandria] => {
    "msg": "See what I mean"
}

NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
alexandria                 : ok=2    changed=0    unreachable=0    failed=0
dgitapp01                  : ok=2    changed=0    unreachable=0    failed=0
piansiapst01               : ok=1    changed=0    unreachable=0    failed=1

 

 

[Joanna Delaporte]

If we need to file a bug on this, please tell me where. It is important to me that this feature work.

[Brian Coca]

I cannot reproduce the issue in 2.0.1, when I hit A it exits the play.

----------

Brian Coca

[Joanna Delaporte]

I just upgraded my Ansible to follow development yesterday after seeing a bug report that had been closed with a patch. I'll test again when I'm on campus Thursday.

Thanks!
Joanna

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/xzetdZ7LA9U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CACVha7cZtUObLm3G1SCtV%3DFVwTKqqo78AXnVX%3DC%3DjS%3D45fJE7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.