# Ansible state seems to do nothing

**URL:** <https://forum.ansible.com/t/ansible-state-seems-to-do-nothing/23628>\
**Category:** Ansible Project\
**Created:** [February 3, 2017, 10:03am UTC](https://forum.ansible.com/t/ansible-state-seems-to-do-nothing/23628 "2017-02-03T10:03:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonty\_Needham](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@Jonty\_Needham](https://forum.ansible.com/u/Jonty_Needham)\
**Post date:** [February 3, 2017, 10:03am UTC](https://forum.ansible.com/t/ansible-state-seems-to-do-nothing/23628/1 "2017-02-03T10:03:43Z")

</div>

The following state, when run, requires the root password (as expected) then prints:

Using /etc/ansible/ansible.cfg as config file  
SUDO password:

PLAYBOOK: install\_stuff.yml \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
1 plays in install\_stuff.yml

PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

I’m expecting it to either state that some states have passed or failed. What have I got wrong?

---

<div class="post-metadata">

**Author:** ![Johannes\_Kastl](https://avatars.discourse-cdn.com/v4/letter/j/bbe5ce/32.png) [@Johannes\_Kastl](https://forum.ansible.com/u/Johannes_Kastl)\
**Post date:** [February 4, 2017, 8:42pm UTC](https://forum.ansible.com/t/ansible-state-seems-to-do-nothing/23628/2 "2017-02-04T20:42:12Z")

</div>

Add -v or -vvv to your ansible-playbook call to see more info.

And, I have seen this when the hostname I gave does not match anything  
in the inventory.

Johannes

---

<div class="post-metadata">

**Author:** ![jean-yves](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@jean-yves](https://forum.ansible.com/u/jean-yves)\
**Post date:** [February 4, 2017, 10:07pm UTC](https://forum.ansible.com/t/ansible-state-seems-to-do-nothing/23628/3 "2017-02-04T22:07:00Z")

</div>

Hi

One idea :

- Check your rpm database... If rpm -qa hang, you probably have to  
rebuild it

Jean-Yves LENHOF
