Closed chaselgrove closed 3 years ago
Hmm, I don't see the identity file in the ConnectionOpenFailedError
, but there's a dance behind the scenes to try to set that up.
Are you using DataLad v0.13.5 or later? There was a rework of some SSH-related things, and I wonder if somehow the identify file argument got lost in this spot.
I said:
There was a rework of some SSH-related things, and I wonder if somehow the identify file argument got lost in this spot.
No, that doesn't look to be the issue (and wasn't a good guess because that should prevent any setup of the remote). I think the issue is that when we resurrect the orchestrator to fetch a job, it doesn't trigger the above code that sets up a custom identity file.
Fetching the job results for a datalad-pair orchestrated job on an aws-ec2 instance fails with:
2020-11-24 16:40:14,942 [ERROR ] ConnectionOpenFailedError: 'ssh -fN -o ControlMaster=auto -o ControlPersist=15m -o ControlPath=/home/ch/.cache/datalad/sockets/bc54bd86 ubuntu@3.238.172.53' failed with exitcode 255 [Failed to open SSH connection (could not start ControlMaster process)] [sshconnector.py:open:541] (ConnectionOpenFailedError)
To reproduce:
This AMI is CE-LITE; the same happens on ami-07ae3592c03add705 (CE standard).
Using the plain orchestrator works as expected.