Ansible API can not be triggered completely

21 views
Skip to first unread message

jianli bi

unread,
May 9, 2022, 4:13:56 AM5/9/22
to Ansible Development
Hello, Ansible Experts,

We have successfully finished to encapsulate Ansible API into one python file as a simple Python Command line, all tasks are done well when every time we run the command to initiate Ansible playbooks, which illustrates as below:

Ansible Server(Ansible API Python command-line, like ansible-cli.py) ----> Candidate Servers(where actual work done, config change effect on) Ansible Server stores all the Ansible Playbooks.

But if we used ssh to send command to the remote server which has Ansible API python file to trigger all the playbooks, from the logs it shows that all tasks were completed, however no actual work was done, no effect or change on the candidate servers which needs configuration change by Ansible.

Local Host(send "ansible-cli.py" over ssh) ---> Ansible Server(ansible-cli.py) ----> Candidate Servers

It is very strange, if we also set up some API to invoke ansible-cli.py on Ansible Server from other function servers, the same issue still is there, it doesn't work any more.

It seems like some resource issue, or some limitation to make Ansible just to skip/ignore the actual work, or not correct Ansible default configuration, not quite sure about it.

If you have any comment or good idea, that will be more helpful and we will be very grateful and benedictory.

Thanks a lot in advance!

BR//Jerry

Reply all
Reply to author
Forward
0 new messages