tags in the playbook does not take effect

[Hui Kang]

Hi,
When I run the ansible-playbook with tags, it skips the database playbooks. See the output below.

Ansible version: ansible-playbook 2.0.0

---------------------------------------------------------------------------------------------------------------

ansible-playbook -i inventory/all-in-one -e @/etc/kolla/defaults.yml -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml site.yml --tags database
 _______
< PLAY: >
 -------
        \ ^__^
         \ (oo)\_______
            (__)\ )\/\
                ||----w |
                || ||

 ______________
< TASK [setup] >
 --------------
        \ ^__^
         \ (oo)\_______
            (__)\ )\/\
                ||----w |
                || ||

ok: [localhost]
 _______
< PLAY: >
 -------
        \ ^__^
         \ (oo)\_______
            (__)\ )\/\
                ||----w |
                || ||

 _______
< PLAY: >
 -------
        \ ^__^
         \ (oo)\_______
            (__)\ )\/\
                ||----w |
                || ||

 ____________
< PLAY RECAP >
 ------------
        \ ^__^
         \ (oo)\_______
            (__)\ )\/\
                ||----w |
                || ||

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

[Sam Yaple (s8m)]

Hello Hui!

I will check this behaviour with ansible-playbooks 2.0.0 vs the 1.x.x branch. This may have changed.

Thank you for your reports

[Sam Yaple (s8m)]

Hui,

The playbooks are not currently working for a few reasons with 2.0.0 Since that is still under heavy development, I am going to hold off making any changes to the playbooks based on being broken in 2.x until that development slows.

The tags as currently setup work with 1.x, as do the rest of the playbooks. I suggest using that for testing.

We can keep this bug open until we confirm that Ansible 2.0 will not honor the tags in thier current form.

[Sam Yaple (s8m)]

Hello Hui,

This did change, but for other reasons than listed. Ansible 2.x is supposed to have 100% backwards compatibility with existing playbooks, however it still has issues with some of the things we do in our playbooks. Once a tag for Ansible 2.x is available I will begin going through our playbooks to ensure we can work out of the gate with Ansible 2.x