Ansible 1.5.4 breaks variables in vars_files

[Mark Nottingham]

I have a playbook with the following:

  vars_files:

    - "vars/{{ ansible_pkg_mgr }}.yml"

... that works fine in 1.5.3, but 1.5.4 doesn't appear to be able to find it; when one of the variables that should have been imported is referenced, it throws a 'foo is undefined' error.

I can provide a minimal reproduction if it'd be helpful.

[James Cammarata]

This issue was reported the other day and has been fixed in the devel branch:

https://github.com/ansible/ansible/issues/6832

You can grab that patch for now if you'd like (https://github.com/ansible/ansible/commit/9c6dd9f79c6fbed3346b951fc280f30cb6d676ae), which will be included in the next release.

--
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/72edbc94-1dab-4b83-a41e-f141b5d51cb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael DeHaan]

It's not variables, rather, just facts.

But yes, fixed on the development branch.

We do not plan for a 1.5.4 update release at this time seeing 1.6 is due for towards the end of the month.   This *may* change, but I'm thinking probably it will not, since there's a workaround posted in the ticket link above.

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

[Mark Nottingham]

On Saturday, April 5, 2014 2:23:13 AM UTC+11, Michael DeHaan wrote:

It's not variables, rather, just facts.

But yes, fixed on the development branch.

We do not plan for a 1.5.4 update release at this time seeing 1.6 is due for towards the end of the month.   This *may* change, but I'm thinking probably it will not, since there's a workaround posted in the ticket link above.

I'll just stick on 1.5.3 until 1.6.

Thanks!