Bug #16872
closed
Unable to run ansible roles on a host
Description
Steps to Reproduce:
1. Run the following command to create the host in foreman:
ansible -m setup localhost
2. Now edit the host and add an Ansible Role to it. This is done by navigating to Hosts -> Select the host -> edit -> `Ansible Roles` tab -> Select one or more Ansible Roles -> Click Submit
3. Now Go to Hosts -> Select the same Host -> Click on `|>Ansible roles` to run the assigned Ansible roles
4. Task page is shown (screenshot attached) but there is no progress. It gets stuck forever.
Files
| ansible_roles_not_run.png | View ansible_roles_not_run.png | 50.4 KB | |||
| logs | logs | 12.3 KB | |||
| 5256c8bd_o.png | View 5256c8bd_o.png | 125 KB | |||
| production.log | production.log | 91.5 KB |
Updated by Daniel Lobato Garcia about 8 years ago
Please provide more information, like logs from production.log and the proxy, which roles are there, etc... By following these steps I can simply follow them and roles run fine on my setup.
Updated by Tomasz Gromowski about 8 years ago
- File 5256c8bd_o.png 5256c8bd_o.png added
I have the same issue,
In dynflow actions are in state planned(pending),
Updated by Tomasz Gromowski about 8 years ago
Foreman ansible_plugin need foreman-task service in Foreman 1.13
I did not notice that there is an additional service.
I just start foreman-task(dynflow-executor) service and now everything working great.
Updated by Ohad Levy about 8 years ago
- Status changed from New to Feedback
could you please provide more information ? thanks
Updated by Tomasz Gromowski about 8 years ago
What information you need?
I am using foreman on Centos 7,
and i was upgrade foreman from version 1.12 to 1.13, step by step documented here: https://theforeman.org/manuals/1.13/index.html#3.6Upgrade,
After that ansible plugin stop working, i couldn't run puppet role from web.
So i just start foreman-task service
systemctl start foreman-task
And that fix my issue.
I do not know if it's the same problem as was Suresh, but the symptoms look alike.
Updated by Daniel Lobato Garcia almost 8 years ago
Thanks Tomasz - I'll check how can we solve this, perhaps a better error message is all that's needed...
Updated by Suresh Thirugnanasambandan over 7 years ago
- File production.log production.log added
I think Tomasz scenario is different.
This still fails for me.
- rpm -qa | grep ansible
tfm-rubygem-foreman_ansible-1.3.0-1.el7sat.noarch
tfm-rubygem-foreman_ansible_core-0.0.1-3.el7sat.noarch
ansible-2.2.1.0-1.el7.noarch
- rpm -q foreman
foreman-1.13.2.2-1.el7sat.noarch
Attached production.log again.
Updated by Suresh Thirugnanasambandan over 7 years ago
- Status changed from Feedback to New
Updated by Daniel Lobato Garcia over 6 years ago
- Priority changed from High to Normal
Suresh, can you try this? The plugin has significantly changed so I believe it should work well now.
Updated by Suresh Thirugnanasambandan over 6 years ago
@sachin, can you retest this?
Updated by Ondřej Ezr over 3 years ago
- Status changed from New to Rejected
Closing this, as it is too old and we failed to reproduce this.
Feel free to reopen this if you are still facing this issue.