Open Nereis opened 9 years ago
"No such file or directory" can indicate that the ansible command is not available on the PATH.
Are you able to check the PATH is updated correctly when using pip?
It's also possible to specify the full path to the ansible executable using the executable configuration parameter
HI,
I have the same problem with Ansible installed with pip, but i'm using Ansible plugin for Jenkins, in jenkins Configuration Page, i set the correct Path to ansible executables directory in slave machine,
but both steps : "Invoke Ansible Ad-hoc command" and "Invoke Ansible Playbook" reports the same error, and no more details in the console even when i add verbosity option -vvvv
Any idea ?? thx
Ansible 1.9.1 Red Hat Enterprise Linux Server release 6.6 (Santiago) Jenkins plugin : 0.3.1
logs
FATAL: Ansible executable not found, check your installation. Build step 'Invoke Ansible Ad-Hoc Command' marked build as failure FATAL: Ansible executable not found, check your installation. Build step 'Invoke Ansible Playbook' marked build as failure Finished: FAILURE
While running ansible from jenkins with ansible installed with pip, I get the next stacktrace
Everything is working fine when I use the debian packet manager to install ansible with the exact same configuration (I checked the logged command which is also the same). Ansible is working while running it from ssh with jenkins user and pip install.
Version: ansible 1.7.2 pip + apt-get, 1.8.2 pip maven 3.2.3 jenkins 1.553 debian 7