Funny enough, in prior versions and in dev branch, having those facts come 
in via a "vars:" statement in the playbook works.  Most places they're 
being used, they come in via extra-vars, and it wouldn't have been a big 
deal to change this instance to match that, but not working at all would've 
been a big deal.

On Wednesday, December 3, 2014 1:49:49 PM UTC-8, Michael DeHaan wrote:
>
> Also I'd double check that those two vars in the include do not come from 
> facts or inventory.
>
> (That would have been any any-version thing)
>
>
> On Wed, Dec 3, 2014 at 4:38 PM, Brian Coca <[email protected] 
> <javascript:>> wrote:
>
>> a few bugs with variables were present in 1.8.x, could you test with
>> current devel as there are fixes there (soon to be released) that
>> might solve your issue.
>>
>> On Wed, Dec 3, 2014 at 4:31 PM, Ross Becker <[email protected] 
>> <javascript:>> wrote:
>> > So, I have a batch of playbooks that include tasks where the filenames 
>> are
>> > determined by variables;
>> >
>> >  - include: tasks/mytask-{{onevar}}-{{anothervar}}.yml
>> >
>> > This was working up through ansible 1.7.2.   As of ansible 1.8.0 (and 
>> also
>> > tested on ansible 1.8.1) this stopped working;  the variables are no 
>> longer
>> > interpreted, and ansible exits complaining with a message:
>> >
>> > ERROR: file could not read: 
>> /root/work/playbooks/tasks/bar-{{platform}}.yml
>> >
>> >
>> > Below are the bits to reproduce:
>> >
>> > foo.yml:
>> > - hosts: slave
>> >   user: root
>> >
>> >   vars:
>> >     platform: rpm
>> >
>> >   tasks:
>> >     - include: "tasks/bar-{{platform}}.yml"
>> >
>> > tasks/bar-rpm.yml:
>> > - name: install OS package dependencies
>> >   action: yum pkg={{item}} state=installed
>> >   with_items:
>> >     - wget
>> >     - ntpdate
>> >
>> >
>> > hosts.inv:
>> > [slave]
>> > sc-cluster-20-04
>> > sc-cluster-20-05
>> > sc-cluster-20-06
>> >
>> >
>> >
>> > The above case works on all ansible versions up through 1.7.2, and 
>> breaks on
>> > 1.8.0+.  I searched on here a bit regarding this, and found the 
>> suggestion
>> > that variables as part of include filenames would only work if passed 
>> in as
>> > extra vars, as only those would be resolvable early enough.  I tested 
>> that
>> > on 1.7.2 by taking out the "vars:" section and passing the value in as 
>> an
>> > extra var on the command-line.  That test worked on 1.7.2 and earlier, 
>> but
>> > does not work in 1.8.0+.
>> >
>> > Is there any means where this functionality should actually work in 
>> 1.8.x?
>> >
>> > --
>> > 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 [email protected] <javascript:>.
>> > To post to this group, send email to [email protected] 
>> <javascript:>.
>> > To view this discussion on the web visit
>> > 
>> https://groups.google.com/d/msgid/ansible-project/c2604edb-dc50-4770-82e1-d638e099b766%40googlegroups.com
>> .
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> 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 [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/CAJ5XC8kLBbfRctHR2nKSjPu4P_p3d3OGnZxpydRc7qgQEwxwDw%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/9bbe3bab-0c70-4fe9-b52f-281f8cf1e718%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to