usetty = False seems to do the trick as well.
Turning the setting to False removes the -tt option from the ssh command
line arguments
Le jeudi 11 février 2016 à 18:08:05 UTC+1, Brian Coca a écrit :
> There is no need to change ssh.py you can set -T in the ssh arguments
> (globally or for the g
There is no need to change ssh.py you can set -T in the ssh arguments
(globally or for the group/hosts) and it will override the -tt as user
options get appended.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To
Thank you very very very much Matthew, we have the same problem on aix
clients and it is a bloker issuer. I confirm that changing the ssh.py with
-T option fixes the problem.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe fr
It's been a few months since this was posted, but I recently got some
updated information back from IBM and thought I'd share here. This is
specific to using 'ssh -tt' to connect to sshd running on AIX.
>From IBM support:
*Here is a summary of my observations till now -
Matthew,
Thanks, this is great documentation for any other AIX user that hits
this. Keep us posted on the IBM response.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails
>
> Thanks for the explanation Brian.
From the outset, we had setup a user with NOPASSWD in sudoers, so this
never even came up. Just for my own curiosity, I did run an ad-hoc copy
command using a different user that has sudo access, but without NOPASSWD.
I confirmed in the verbose ansible
ttys are needed for privilege escalation (sudo, su, pbrun) when they
prompt for passwords. If you use sudo NOPASSWD or login as root, you
are fine without it.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe fro
OK, I 'think' I've gotten to the root of this particular problem, and it
doesn't appear to have anything to do with python or binaries to generate
checksums.
I was able to reproduce the same command hanging issue by just performing
an SSH with the same arguments that Ansible uses. After proces
