New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oc rsync frequently doesn't return #9726
Comments
I have the same problem with oc v1.3.0-alpha.2. @bdshadow has no issues on Fedora |
yes. My version are: |
@fbricon To help me better understand where the hang is happening, can you:
Thank you much. |
killed log level 5 oc:
ps ax on the node
|
Looking at the logs, seems to me that what hanged was the I did find some people reporting problems with rsync hangs:
|
The hang could also be happening in the second 'oc' process that is initiated by rsync ... since we're using 'oc rsh' as transport. Unfortunately, I haven't been able to reproduce this locally. @fbricon one possible solution would be to expose a --timeout flag that can be passed to the rsync invocation, would this be an acceptable solution? |
@fbricon bump |
Sorry @csrwng, I thought I replied already, but apparently forgot to hit the green button. So, a timeout flag could be useful in any case, but it's gonna be hard to determine a proper value for a it. |
Thanks @fbricon, I'll put together a PR so you can try it out and see if it works for you. The |
Yeah that's what I was thinking too. Still, if rsync'ing a large file takes too long, well, it's not gonna play well |
Thanks @fbricon for trying it out. The hang is still happening since rsync seems to ignore the --timeout when delegating to the transport call, which is ultimately what's stuck. Thread dump from oc rsh (invoked by rsync -e 'oc rsh'): @ncdc can you please take a look at that thread dump and see if there's something that you recognize that could be going on? |
The thread dump shows that the remote command execution has finished ( I don't know offhand why the node would close the error stream but keep the stderr stream open (which is what's happening here). I would recommend running |
I was able to reproduce the problem without MacOS.
|
@fbricon or @jeffmaury are you able to reproduce with the debug information that @ncdc requested? Any help in tracking this down is greatly appreciated. |
@fbricon I'm still not able to reproduce this bug on my end. I will close it for now. If you get a chance to run with the debug env var on and reproduce it, please reopen it so we can further investigate. |
@ncdc sorry for the late reply, but this is the debugging info I got with the help from @csrwng https://gist.github.com/fbricon/f387246d6e070a99466ab30486d540e3 |
@ncdc with the server-side stack dump, I can see the API server copying from the client to the kubelet. However, I don't see any evidence of a connection open on the kubelet side:
@fbricon what version of the server are you running? |
For CLI, I use oc v1.3.0-Alpha3 And then the web console tells me: That's the version of openshift shipped with the official CDK 2.1 release |
@fbricon I'm wondering if it's an issue with the back-end. Would you be willing to try a different back-end with the latest origin build? I will e-mail you the details. |
This hasn't been updated in a long time, so I'm going to close it. Feel free to reopen if necessary. |
JBoss Tools OpenShift tools delegates workspace to pod synchronization to oc rsync. More often than not, the oc rsync command doesn't return, leaving the process hanging, waiting for a return code, at least on OSX 10.10.5 (Yosemite).
I managed to reproduce the problem by executing the exact same command from a terminal. In that particular example, the pod is sync'ed to the local directory:
Version
oc v1.2.0
kubernetes v1.2.0-36-g4a3f9c5
rsync version 2.6.9 protocol version 29
Steps To Reproduce
Current Result
rsync command doesn't always return
Expected Result
rsync command should return 100% of the time
Additional Information
In http://screencast.com/t/pTPUEVppqp4, you can see the 1st command gets stuck. After killing it, other commands work, until it gets stuck again at the end.
This issue was reported under https://issues.jboss.org/browse/JBIDE-22677
Sometimes, the rsync command gets stuck when rsync'ing from local to the pod
The text was updated successfully, but these errors were encountered: