The same vmId error came back when we tried some more tags-related things. Not sure why tags tickle it, but it seems there's an issue with how ansible calls the azure SDK (https://github.com/ansible/ansible/pull/22974). We can confirm that merging this fix resolves the issues we're having in devel and stable-2.3, and does not appear to introduce any new issues. Hope it gets picked up for a merge into 2.3 final...
On Wednesday, April 12, 2017 at 1:13:50 AM UTC+2, 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/64cf6f0d-eb30-4611-b715-3769adb0032f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
