You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2019. It is now read-only.
The push requires my host key which is forwarded. Works fine manually from the guest and other Ansible commands that don't require key work fine too.
I suspect there is some ssh config/variable somewhere within vlad that is missing from the custom role or it's a vmware issue. Hoping there's an easy fix.
Any help much appreciated!
Thanks
Rich
The text was updated successfully, but these errors were encountered:
richierampage
changed the title
SSH forwarding for custom role on VMware
SSH forwarding not working for custom role on VMware
Feb 11, 2016
Hi Rich. One way to test if your key has been successfully forwarded is to run the following command from the guest:
ssh-add -L
If successfully forwarded it should return the contents of the forwarded public key file. Hopefully that can help narrow down what's going on with your custom playbook.
My issue was that I was trying to do too much with the Vlad custom role with other hosts. I was trying to ssh to a server via vlad, so vagrant key was failing even if ssh passthrough is working.
I have now split out my server/deployment stuff into a separate playbook which works fine.
Running ssh-add would be good to add as a local task option, I have to do it everytime I reboot my mac else passthrough doesn't work. I will do a pr if I do it.
Hi,
I can't get ssh forwarding to work for a task within my custom role.
- command: git push -u origin --all
args:
chdir: /var/www/site/docroot
removes: "/var/www/site/docroot/.git"
register: dir
- debug: var=dir.stdout_lines
The push requires my host key which is forwarded. Works fine manually from the guest and other Ansible commands that don't require key work fine too.
I suspect there is some ssh config/variable somewhere within vlad that is missing from the custom role or it's a vmware issue. Hoping there's an easy fix.
Any help much appreciated!
Thanks
Rich
The text was updated successfully, but these errors were encountered: