-
Notifications
You must be signed in to change notification settings - Fork 40k
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
kubectl exec doesn't return command exit code #26424
Comments
@sttts i am trying kubectl 1.2.4 and i see
|
@dims that's right. But the return code in the shell of the whole command is 1, compare |
@sttts ack, just making sure we are seeing the same thing :) |
Haven't looked into the code yet. Not sure cobra supports that. |
@sttts looks like kubelet itself is treating exit code and the error stream as one thing. This will take some non-trivial work i think |
@sttts - just for error stream. yes, i think that would be good! |
Yes that's what I had been thinking as well. On Monday, May 30, 2016, Dr. Stefan Schimanski notifications@github.com
|
Do you want to bundle this in with my terminal resizing pull, or try to On Monday, May 30, 2016, Andy Goldstein agoldste@redhat.com wrote:
|
@ncdc working on it right now. Makes sense to put that on-top of your PR. |
Looks like PR #26541 is close to merging. |
Waiting for #25273 to go in. |
|
The last line should be 5.
The text was updated successfully, but these errors were encountered: