Red Hat Bugzilla – Bug 818330
Git/ssh error on git clone GIT_URL: ControlPath too long
Last modified: 2015-05-14 21:52:57 EDT
Description of problem:
See forum post:
This user ran into a very specific ssh error:
$ git clone GIT_URL
Cloning into 'myapp'...
ControlPath too long
fatal: The remote end hung up unexpectedly
Added the following to ~/.ssh/config:
For this enhancement, should we include this into our rhc client tool's ssh environment config? Does it hurt?
Please note that this is the first time I've seen this exact error, but I haven't been *looking for it.
Changing the ControlPath means that multiple SSH agents might collide - I don't think restricting it this way is a good idea. We might be able to shorten the hostname or user. I think if they followed these steps they would only be able to ssh/git on one process at a time
Can you document this as a workaround in the KB for now?
I opened a KB article for this. https://openshift.redhat.com/community/kb/kb-e1046-unable-to-git-clone-an-application-when-ssh-multiplexing-is-in-use-controlpath-too-long. We have no easy path to implement this in the CLI and changing the Git URL is fairly expensive. Not many folks have hit this.
Since there's a KB for this, and according to comment 2, close it as won't fix.