Limiting hosts when including playbooks stopped working in 1.8

[Wolfgang Ziegler]

Hi!

I'm using the pattern outlined at https://github.com/ansible/ansible/pull/1956 to include playbooks for a limitted group of hosts. In short:

 
 ---
 # configure-webservers.yaml
 - name: configure the webservers
   hosts: webservers:&$hosts tasks: ...

 ---
 # Configure staging server
- include: configure-webservers.yaml hosts=staging

However, this stopped working when upgrading to ansible 1.8.1. Is this a bug, or is passing variables to playbook includes like that not supported any more?

If it's not supported any more, any other suggestions on how to do this?

My use case is a rather general provising playbook - including multiple roles and possibly some custom tasks - which I want to be able to dynamically apply to some hosts from a playbook run. It shouldn't apply to "all" hosts though.

Best regards,
Wolfgang

[Wolfgang Ziegler // fago]

I figured, the variabel replacement still works fine - but for some reason the host groups are not forwarded to the included playbook anymore. E.g., in root playbook the host is in group "mygroup", but when the included playbook runs for "mygroup" the host is not matched any more. The output is like this:

PLAY ["mygroup"] **************************************************************
skipping: no hosts matched

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/c8bdwPtR640/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/03e0501f-ade6-4a4d-ae3a-59cc9eba118c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael DeHaan]

Ansible hasn't used a dollar sign for variable replacement in a long time

Try

{{ hosts }}

--
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-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL0uX3SK3kNtTAnaocPFQ7moBDUEhat6NbZ66w2Pr3_3SN9EBw%40mail.gmail.com.

[Wolfgang Ziegler]

Sure, I've been using {{ hosts }} - I just copied the example from the old docs - sry for that. I did some more testing and think this is a bug. I reported it with a simple example playbook at https://github.com/ansible/ansible/issues/9733

[Michael DeHaan]

Where did you define the 'my group' variable?

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/492b382f-7567-41ec-8e80-ac0c4d28cabc%40googlegroups.com.

[Wolfgang Ziegler]

As noted in the example over at https://github.com/ansible/ansible/issues/9733 I'm setting the host-group when including the playbook like this:

- include: test-include.yml hosts="group"

[Michael DeHaan]

Yeah the scope is wrong on this one - You can't do that.

If it happened to work like this before, it would be an accident :)

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/6f593126-9555-4f24-9a26-3e8040dc8ec1%40googlegroups.com.

[Michael DeHaan]

Perhaps you meant this was a playbook level include -- which perhaps should.

Can we see the top level playbook in entirety?

[Wolfgang Ziegler]

Yes, it's a playbook level include. It looks like the following:

---
- hosts: devserver
  sudo: yes
  tags: devserver, provision
  tasks:
    -  sometasks

- include: "../devsetup/provision.yml hosts=ci-container"

- include: ci-container.yml

Hope that helps,

thank you,
Wolfgang