Thanks Brian. I roughly binary searched and the behavior seems to have broken between Ansible code versions v1.9.4-1 and v2.0.0-0.1.alpha1.
Before, --list-tasks would show individual tasks and no 'meta' tasks. At 2.0, it just shows a shorter list of meta tasks, which breaks --start-at-task. Unfortunately, that range is pretty big: ansible (2df6513f8d802a931e0fa88afa6dc019ba4bd6e6) 14091 $ git log --pretty=oneline v1.9.4-1..v2.0.0-0.1.alpha1 | wc -l *2336* Over two thousand commits. I'll try to bin search it, since it's a huge pain for me to debug large Ansible runs without --start-at-task. Brian, how should I report this to increase the chance that it gets acknowledged? It's known broken since Jul 21: https://github.com/ansible/ansible/issues/11692 ... but I can't reopen that bug. Should I report a new bug and link to the closed one, or can you reopen it? Thanks, Brandon On Monday, November 30, 2015 at 5:16:29 PM UTC-8, Brian Coca wrote: > > the 'meta' tasks you see there might be the internal calls to `meta: > refresh_handlers` which don't normally have a name. List tasks in 2.0 > shows these, they did not appear in previous versions. > > > -- > Brian Coca > -- 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/32e26217-89cc-468e-87bb-3a478b3e3024%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
