As it turns out, this seems to have more to do with the fact that VM updates don't seem to work. I was able to repro this with a simpler playbook that had nothing to do with the templating:
https://github.com/ansible/ansible/issues/23765 and found a similar issue(https://github.com/ansible/ansible/issues/20444), which actually already has a fix (https://github.com/ansible/ansible/pull/22974), it just hasn't been merged yet. Applying that fix makes the tag issue go away as well. It's a very simple fix, so it would be nice if it could get merged. thanks, Bjørn On Tuesday, April 11, 2017 at 4:13:50 PM UTC-7, Matt Davis wrote: > > Possibly- if you're running from source, make sure you're running the > hacking/env-setup script each and every time you pull new changes in. > Otherwise there can be stale .pyc files and other things laying around that > can wreak all sorts of havoc (the script cleans all that up). > > On Friday, April 7, 2017 at 10:59:22 PM UTC-7, [email protected] > <javascript:> wrote: >> >> So, here's the kicker... >> >> Switched from devel to stable-2.3, and I'm able to provision using the >> templated tags. Switch back to devel, and I'm still able to use the >> templated mechanism. >> >> So, probably not a bug. Rather, some edge case interplay between the >> various python dependencies? >> > -- 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/026622a6-e280-478b-a160-9eacb73a81c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
