*Here's my minimal test case, which has one task.* 

The task comes from an include, which seems to be the issue.  Yes, roles 
are great and we try to use them as much as possible, but our codebase has 
a number of places where includes are used to define tasks lists.

Brian, please let me know what to do next.  Thanks.

*Files (common to both versions):*

[19:50:41 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14366 $ cat site-simple.yml 

---

- hosts: docker_singlebox

  gather_facts: false

  tasks:

    - name: Test task direct

      file: path="path" state=directory

    - include: include/file_to_include.yml

[19:50:45 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14367 $ cat include/file_to_include.yml 

---

- name: Test task

  file: path="path" state=directory

[19:51:02 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14367 $ cat inventory/my_host.ini 

[docker_singlebox]

192.168.99.100:2222


*With v2.0.0-0.1.alpha1:*


[19:51:05 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14367 $ ansible-playbook -f 20 -i 
inventory/my_host.ini site-simple.yml --start-at-task="Test task"


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


PLAY RECAP 
*********************************************************************


*Note that the task was not run (or found) when included, but when directly 
provided, is found.*


[19:51:22 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14367 $ ansible-playbook -f 20 -i 
inventory/my_host.ini site-simple.yml --start-at-task="Test task direct"


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


TASK [Test task direct] 
********************************************************

ok: [192.168.99.100]


TASK [include] 
*****************************************************************

included: include/file_to_include.yml for 192.168.99.100


TASK [Test task] 
***************************************************************

ok: [192.168.99.100]


PLAY RECAP 
*********************************************************************

192.168.99.100             : ok=3    changed=0    unreachable=0    
failed=0   


*Probably related to this:*


[19:48:24 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14363 $ ansible-playbook -f 20 -i 
inventory/my_host.ini site-simple.yml --list-tasks


playbook: site-simple.yml


  PLAY: #1

    tasks:

      TASK: meta 

      TASK: Test task direct

      *TASK: include*

      TASK: meta

      TASK: meta


*After changing to v1.9.4-1:*


[19:51:52 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14367 $ ansible-playbook -f 20 -i 
inventory/my_host.ini site-simple.yml --start-at-task="Test task direct"


PLAY [docker_singlebox] 
******************************************************* 


TASK: [Test task direct] 
****************************************************** 

ok: [192.168.99.100]


*TASK: [Test task]* 
************************************************************* 

ok: [192.168.99.100]


PLAY RECAP 
******************************************************************** 

Test task direct -------------------------------------------------------- 
1.21s

Test task --------------------------------------------------------------- 
0.10s


Playbook finished: Mon Nov 30 19:52:55 2015, 2 total tasks.  0:00:01 
elapsed. 


192.168.99.100             : ok=2    changed=0    unreachable=0    
failed=0   


[19:52:55 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14367 $ ansible-playbook -f 20 -i 
inventory/my_host.ini site-simple.yml --start-at-task="Test task"


PLAY [docker_singlebox] 
******************************************************* 


TASK: [Test task] 
************************************************************* 

ok: [192.168.99.100]


PLAY RECAP 
******************************************************************** 

Test task --------------------------------------------------------------- 
0.11s

Test task direct -------------------------------------------------------- 
0.00s


Playbook finished: Mon Nov 30 19:52:58 2015, 2 total tasks.  0:00:00 
elapsed. 


192.168.99.100             : ok=1    changed=0    unreachable=0    
failed=0   


[19:52:58 Mon Nov 30] brandonh@brandonh-macbook.local 
~/src/fwd/ops/ansible/fwd-ubuntu

fwd-ubuntu  (testing/alex/docker) 14367 $ ansible-playbook -f 20 -i 
inventory/my_host.ini site-simple.yml --list-tasks


playbook: site-simple.yml


  play #1 (docker_singlebox): TAGS: []

    Test task direct TAGS: []

    *Test task TAGS: []*




On Monday, November 30, 2015 at 7:03:33 PM UTC-8, Brandon Heller wrote:
>
> Brian, can you point me to the tests you're running?
>
> As an update to the previous, I gave up on binary searching to find where 
> the behavior changed; the issue is present at v2.0.0-0.1.alpha1~250 but 
> before then I see a compilation issue where Ansible thinks quotes are 
> missing.
>
>
> On Monday, November 30, 2015 at 6:54:41 PM UTC-8, Brian Coca wrote:
>>
>> Closed bugs don't normally get read. 
>>
>> If you can provide a minimally reproducible test case, we can look into 
>> it.
>>
>> My tests show this feature working.
>>
>

-- 
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 ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/524d2ce6-c2ba-4f60-aa88-bbd975d43a54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to