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
I noticed that when running a auth or mount , eg ./ac --host-mount --host "...." , if the managed node is unresponsive the wait for a time could be 5+ minutes, we should put a timer/loop around this logic or do a ping test first before even trying so that we fail fast and move on. A command with 45 managed nodes and 5 failures could add nearly an hour of wait time.
It will just hang on that till there is a connection timeout and move onto the next machine.
INFO: Copy SSH keys to the managed node xxxx
-----------------------------------------------------------------------
Copying public key /root/.ssh/id_ed25519.pub to host xxxx.xxx.xxx.xxx.com
Copying public key /root/.ssh/id_rsa.pub to host xxxx.xxx.xxx.xxx.com
ssh: connect to host xxxx.xxx.xxx.xxx.com port xx: Connection timed out
Ansible module
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Enabler description
I noticed that when running a auth or mount , eg
./ac --host-mount --host "...."
, if the managed node is unresponsive the wait for a time could be 5+ minutes, we should put a timer/loop around this logic or do a ping test first before even trying so that we fail fast and move on. A command with 45 managed nodes and 5 failures could add nearly an hour of wait time.It will just hang on that till there is a connection timeout and move onto the next machine.
Ansible module
No response
The text was updated successfully, but these errors were encountered: