Issue 1:
Issue Type:

Bug Report

Ansible Version:

ansible 2.0.1.0
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides

Ansible Configuration:

No changes

Environment:

CentOS 7 managing CentOS7

Summary:

--start-at-step switch doesn't work

Steps To Reproduce:

https://github.com/goozbach/ansible-steps

Use this playbook to execute the following command:

ansible-playbook -i inv/ site.yml --start-at-task=bar

Expected Results:

The playbook would start at the 'bar' task and complete from there:

[vagrant@localhost steps]$ ansible-playbook -i inv/ site.yml

PLAY [step broken] *************************************************************

TASK [bar] *********************************************************************
ok: [localhost] => {
"msg": "bar"
}

TASK [baz] *********************************************************************
ok: [localhost] => {
"msg": "baz"
}

TASK [qux] *********************************************************************
ok: [localhost] => {
"msg": "qux"
}

PLAY RECAP *********************************************************************
localhost : ok=3 changed=0 unreachable=0 failed=0

Actual Results:

Play doesn't run any tasks:

[vagrant@localhost steps]$ ansible-playbook -i inv/ site.yml --start-at-task=bar

PLAY [step broken] *************************************************************

PLAY RECAP *********************************************************************```

Issue 2:
Issue Type:

Bug Report

Ansible Version:

ansible 2.1.0 (detached HEAD 61f05c2e8d) last updated 2016/03/16 14:59:29 (GMT -700)
lib/ansible/modules/core: (detached HEAD 345d9cbca8) last updated 2016/03/16 14:59:37 (GMT -700)
lib/ansible/modules/extras: (detached HEAD f47b499bb9) last updated 2016/03/16 14:59:37 (GMT -700)

Ansible Configuration:

Environment:

OSX El Capitan

Summary:

--start-at-task non-functional since sometime after 2.0.0.2. Currently broken in stable-2.0 and devel.

Steps To Reproduce:

Run the sample playbook below with ansible-playbook playbook.yml --start-at-task "start here". All tasks in the first play will be skipped (except setup), and all tasks in subsequent plays will run (including setup). Suspect this is related to the "when do we run setup" changes w/ tags, but haven't had time to dig into it yet.

- hosts: localhost
tasks:
- name: skip me
debug: msg="shouldn't see this"
- name: start here
debug: msg="should start here"
- name: run also
debug: msg="run me too"

- name: second play
hosts: localhost
tasks:
- name: this should run
debug: msg="first task new play"

Expected Results:

First task in first play is skipped, all others run

Actual Results:

All tasks in first play skipped, all others run

PLAY [localhost] ***************************************************************

TASK [setup] *******************************************************************
ok: [localhost]

PLAY [second play] *************************************************************

TASK [setup] *******************************************************************
ok: [localhost]

TASK [this should run] *********************************************************
ok: [localhost] => {
"failed": false,
"msg": "first task new play"
}

PLAY RECAP *********************************************************************
localhost : ok=3 changed=0 unreachable=0 failed=0