# ERROR! no action dected in task.  os\_server\_action action: rebuild

**URL:** <https://forum.ansible.com/t/error-no-action-dected-in-task-os-server-action-action-rebuild/25780>\
**Category:** Ansible Project\
**Created:** [October 19, 2017, 3:27pm UTC](https://forum.ansible.com/t/error-no-action-dected-in-task-os-server-action-action-rebuild/25780 "2017-10-19T15:27:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pete\_Pedersen](https://avatars.discourse-cdn.com/v4/letter/p/f04885/32.png) [@Pete\_Pedersen](https://forum.ansible.com/u/Pete_Pedersen)\
**Post date:** [October 19, 2017, 3:27pm UTC](https://forum.ansible.com/t/error-no-action-dected-in-task-os-server-action-action-rebuild/25780/1 "2017-10-19T15:27:18Z")

</div>

Hi all,

I’m using Ansible Tower, 2.3.1.0, with Python 2.7.5.

I wrote the following playbook to automate rebuilding of servers with new images.

---

<div class="post-metadata">

**Author:** ![Pete\_Pedersen](https://avatars.discourse-cdn.com/v4/letter/p/f04885/32.png) [@Pete\_Pedersen](https://forum.ansible.com/u/Pete_Pedersen)\
**Post date:** [October 25, 2017, 8:21pm UTC](https://forum.ansible.com/t/error-no-action-dected-in-task-os-server-action-action-rebuild/25780/2 "2017-10-25T20:21:27Z")

</div>

I found a solution to this. There is an alias for the module called os\_server\_action **s** and I found if I used that, the playbook ran as expected.