ansible-playbook stops after include

Here is what I’m trying with ansible 2.0.0 (dev from earlier this week)

what is qt5 doing? does altering the order change the results?

So what I posted before was a simplification to do everything separately.
Initially, I had a role whose main.yml task includes qt.yml and wx.yml (which are next to main.yml, in roles/common/tasks/)

The qt.yml is:

This configuration works fine with 1.9.2 though.

-vvvv output shows what?

The output shows no errors, nothing seems wrong.

Running this playbook in devel, after qt5.yml is run, execution stops. If I reverse the order, it only runs wx_widgets.yml.
Running this playbook in v1.9.3-0.3.rc3 results with both included playbooks being executed properly.

I simulated the execution order with 2 simpler playbooks (simply touching files on the desktop) and they both get executed properly in devel.

So maybe it’s something with the modules I’m using in wx_widgets.yml or qt5.yml but they don’t have any obvious errors, and whichever one is run first DOES get installed properly with no errors.
The only modules the playbooks use are:
apt_repository, apt_key and apt.

I thought maybe I was including things incorrectly, but then testing it in 1.9.3 showed it worked they way I was trying to nest includes. So I’m confused.

I don’t mean to hijack this thread, but I thought I should mention I’m having exactly the same problem. Worked in Ansible 1.9.3, in 2.0.0 it runs through all the tasks/roles in the first couple of includes and then stops (with a play recap), all without any errors.

I’m glad you joined in, I never resolved this or got back around to this problem.
I couldn’t get any useful info about what was causing it either. I made a few super simple examples, but of course they ran fine.
Part of my experiment involved running each include individually, which worked so I was stymied.

Here’s the content of my parent playbook:

As a quick follow-up on this, I since tried rolling back to stable-1.9 and also the 1.9.3 tag as well, and interestingly neither of those would execute past a specific point in my base.yaml playbook. When it reaches the specific task, ansible hangs…if I comment out this task and re-run, it then gets to the next task in the order but hangs on that one.

So, the plot thickens. In any case, this is really causing problems for me as I have to run all my playbooks individually, and I might have to look at breaking my base.yml up into different playbooks as it now doesn’t complete.