Really confused - permission denied via Sempahore not via Ansible CLI some (but all rpi hosts) hosts. #1687
Replies: 1 comment
-
I've looked into this further and understand what is going on, or worked around it. I basically create a clone of my inventory file and added the sudo credentials for that group of hosts and then deuplicated the task to use that variation of the inventory - it works. I looked at 'include' in the script but it will inherit the inventory from the parent so that doesn't work. I'm not sure if this is a great set-up or not. I've gone from 1 script direct in the ansible CLI to having multiple tasks and inventories to cover each permuation of my homelab. i.e. a variation of tasks / inventory for RPIs'. Will need to do the same again for my Synology too. |
Beta Was this translation helpful? Give feedback.
-
I'm just getting started with Semaphore and have some simple ansible scripts.
Using the exact Ansible cli script / host files contents the script runs fine, (its just a basic log into all but varied hosts and ping).
I translated and setup the same script in Semaphore and half of the hosts fail to connect with 'host unreachable / invalid password: permission denied".
Note my host file via CLI and Inventory are exactly the same. The script via CLI and the task template is exact the same. I can run the Ansible CLI scripts straight after this error and it works fine.
What is even more odd which I find confusing is that its my raspberry pi hosts that are failing, not all hosts. Aside from the RPI hosts the carbon copy scripts from Ansible CLI into Sempahore work fine.
My Semaphore setup is a docker container. From the docker container directly and the docker host I can manually ssh to each of these RPI hosts with the same credentials in the inventory file.
The other hosts are a mix of debian / redhat virtual and physical hosts which work.
Appreciate any tips or advise - I find this really puzzling.
Beta Was this translation helpful? Give feedback.
All reactions