# Bug in top-level playbook: tags broken

**URL:** <https://forum.ansible.com/t/bug-in-top-level-playbook-tags-broken/18403>\
**Category:** Ansible Project\
**Created:** [June 4, 2015, 11:21am UTC](https://forum.ansible.com/t/bug-in-top-level-playbook-tags-broken/18403 "2015-06-04T11:21:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jang](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@jang](https://forum.ansible.com/u/jang)\
**Post date:** [June 4, 2015, 11:21am UTC](https://forum.ansible.com/t/bug-in-top-level-playbook-tags-broken/18403/1 "2015-06-04T11:21:54Z")

</div>

See the attachment. With ansible 1.7.2 this works as expected:

% ansible-playbook --version  
ansible-playbook 1.7.2  
% ansible-playbook -i hosts/localhost a.yml --tags b

PLAY [localhost]

> **(attachments)**
>
> [x.tar.gz](https://forum.ansible.com/uploads/short-url/ifXocp8ZL3UaDvGTgHaD5bJiL21.gz) (308 Bytes)

---

<div class="post-metadata">

**Author:** ![jang](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@jang](https://forum.ansible.com/u/jang)\
**Post date:** [June 4, 2015, 11:25am UTC](https://forum.ansible.com/t/bug-in-top-level-playbook-tags-broken/18403/2 "2015-06-04T11:25:49Z")

</div>

On this subject, we've found a bunch of regressions where ansible's  
playbook semantics (especially when it comes to the behaviour of variables  
in included roles) don't appear to be nailed down.

Is there a regression framework for test cases? I'm happy to submit a set  
of playbooks that illustrate the variability we're seeing. At the moment  
we're kind of in the position of having to choose which set of bugs is the  
least egregious 🙂

Cheers,  
jan

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [June 5, 2015, 1:53pm UTC](https://forum.ansible.com/t/bug-in-top-level-playbook-tags-broken/18403/3 "2015-06-05T13:53:54Z")

</div>

There is an open ticket already on this issue  
[https://github.com/ansible/ansible/issues/9862](https://github.com/ansible/ansible/issues/9862).