OK, with an RPM built last weekend it still works just fine for me... $ rpm -q ansible ansible-1.9-0.git201502131321.el7.centos.noarch
$ ansible --version ansible 1.9 configured module search path = None $ ./scripts/newvm mptest.satapp PLAY [vmcreate] *************************************************************** TASK: [Check for required variables] ****************************************** skipping: [local] TASK: [Check for vSphere access parameters] *********************************** skipping: [local] TASK: [Create VM from template] *********************************************** changed: [local] My play looks like: https://gist.github.com/phips/7c25ccc74f2aee268ed8 On Wednesday, 18 February 2015 17:26:50 UTC, Mark Phillips wrote: > > Worth checking ;-) > > I've been using the template stuff since late December, and it's working > all fine. However, saying that, I've not tried a recent code base. Is your > 1.9 pull really recent? I'll try a bang up to date pull and see if I get > the same... > > On Wednesday, 18 February 2015 17:20:42 UTC, John-Paul Herold wrote: >> >> A very valid question haha, but no I do not. I've tested it locally on my >> laptop, as well as an ansible control box I have in the same environment as >> my vsphere cluster. >> > -- 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/e949a336-8f77-43b6-9d4b-7b55e34c2060%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
