# strange and broken behavior in 1.4 **URL:** \ **Category:** Ansible Project\ **Created:** [November 23, 2013, 1:59am UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983 "2013-11-23T01:59:07Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\ **Post date:** [November 23, 2013, 1:59am UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/1 "2013-11-23T01:59:07Z")
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. ---
**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\ **Post date:** [November 23, 2013, 2:03am UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/2 "2013-11-23T02:03:45Z")
Also, I should add that I built from git: $ git checkout v1.4.0 $ python setup.py bdist\_rpm ---
**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\ **Post date:** [November 23, 2013, 2:39am UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/3 "2013-11-23T02:39:10Z")
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. ---
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [November 23, 2013, 3:17am UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/4 "2013-11-23T03:17:54Z")
You have a crossed up install, template module works fine. Try on a clean box or something? – Michael ---
**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\ **Post date:** [November 23, 2013, 7:25am UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/5 "2013-11-23T07:25:58Z")
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](https://gist.github.com/davidbirdsong/7611851) If I use the included spec file: [https://gist.github.com/davidbirdsong/7611838](https://gist.github.com/davidbirdsong/7611838) ---
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [November 23, 2013, 3:44pm UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/6 "2013-11-23T15:44:07Z")
“python setup.py bdist\_rpm, I get this error:” You need to run “make rpm” instead, as you are skipping too many steps. [https://github.com/ansible/ansible/blob/devel/Makefile](https://github.com/ansible/ansible/blob/devel/Makefile) ---
**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\ **Post date:** [November 24, 2013, 3:58am UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/7 "2013-11-24T03:58:53Z")
> "python setup.py bdist\_rpm, I get this error:" > > You need to run "make rpm" instead, as you are skipping too many steps. > > [https://github.com/ansible/ansible/blob/devel/Makefile](https://github.com/ansible/ansible/blob/devel/Makefile) 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. ---
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [November 24, 2013, 4:00pm UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/8 "2013-11-24T16:00:03Z")
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. ---
**Author:** ![David\_Birdsong](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Birdsong](https://forum.ansible.com/u/David_Birdsong)\ **Post date:** [November 24, 2013, 10:42pm UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/9 "2013-11-24T22:42:00Z")
> 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. ---
**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\ **Post date:** [November 25, 2013, 3:45pm UTC](https://forum.ansible.com/t/strange-and-broken-behavior-in-1-4/13983/10 "2013-11-25T15:45:48Z")
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.