After upgrading to 1.4 (from HEAD from like 2 weeks ago), my playbooks are failing to run:
ERROR: template is not a legal parameter in an Ansible task or handler
template is the first task, so I comment that out:
ERROR: yum is not a legal parameter in an Ansible task or handler
yum being the second, comment that out:
ERROR: file is not a legal parameter in an Ansible task or handler
…this just keeps going.
I’ll attempt to downgrade and see if that helps.
Also, I should add that I built from git:
$ git checkout v1.4.0
$ python setup.py bdist_rpm
I noticed that by building the rpm myself, I missed some dependencies, so I resolved that by forcing paramiko, jinja2, and babel to be installed on a fresh host. The problem follows to a clean, new instance.
I downgraded to 1.3.4 and the problem goes away.
You have a crossed up install, template module works fine. Try on a clean box or something?
– Michael
Installing the RPM on a fresh host causes the same error.
I think there’s something broken w/ just the RPM packaging.
If I download the release tarball and try to build an rpm from it in the top level dir:
python setup.py bdist_rpm, I get this error:
https://gist.github.com/davidbirdsong/7611851
If I use the included spec file:
https://gist.github.com/davidbirdsong/7611838
“python setup.py bdist_rpm, I get this error:”
You need to run “make rpm” instead, as you are skipping too many steps.
"python setup.py bdist_rpm, I get this error:"
You need to run "make rpm" instead, as you are skipping too many steps.
It used to be so much easier to build the rpm. I'm getting hung up on not
having a2x, so I guess I'll wait until 1.4 shows up in epel.
Yeah, that’s completely not the case, because we’ve always used asciidoc and nothing has changed here.
I would also like to nominate this thread topic as pretty terrible for describing the subject of the thread.
Yeah, that's completely not the case, because we've always used asciidoc
and nothing has changed here.
Yeah, I was off doing my own thing with calling setup.py directly. Whatevs,
I can't expect support on that.
I would also like to nominate this thread topic as pretty terrible for
describing the subject of the thread.
I'd take it back if I could, but I went from a working playbook to a
seemingly broken one by upgrading which seemed damning at the time.
I’m suggesting the topic actually say something about the email thread.
“ERROR: template is not a legal parameter in an Ansible task or handler”
Would have been a good subject.