I think I found the problem in my code:
If I include the role tmp in my playbook using
- { role: tmp, tags: update }
it seems like all tasks of the role are executed, and the tags are not
respected.
If I put the role in the playbook without denoting a tag, the tags are
respected if specified in the ansible-playbook command, e.g. using --tags
"update"
Is this intended behaviour or a bug?
On Tuesday, June 10, 2014 8:59:12 PM UTC+2, Michael Hauck wrote:
>
> I have a problem that I want to execute only tasks with certain tags from
> a playbook, but this does not work.
>
> My playbook looks as follows:
>
> #playbook.yml
> - hosts: appservers
> remote_user: myuser
> roles:
> - { role: tmp, tags: update }
>
> The tmp role task file looks as follows:
>
> # roles/tmp/tasks/main.yml
> - name: Test 1
> debug: msg="Test 1"
> tags: anothertag
>
> - name: Test 2
> debug: msg="Test 2"
> tags: update
>
>
> If I execute the playbook with
>
> ansible-playbook -i inventory/test playbook.yml
>
> or
>
> ansible-playbook -i inventory/test playbook.yml --tags=update
>
> all two tasks are executed both times.
> I do not want task "Test 1" to be executed.
>
> I can achieve this by running ansible-playbook with the option
> --skip-tags=anothertag, but this not what I want.
> Do you know how I can get that to work or where my scripts are erroneous?
>
> Thanks,
> Michael
>
--
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/486c6fcf-9f5e-4bcc-88b8-9a2b8afe4d3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
