Skip to content
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

Running exec and attach example get 400 Bad request #481

Closed
lephix opened this issue Jan 9, 2019 · 10 comments
Closed

Running exec and attach example get 400 Bad request #481

lephix opened this issue Jan 9, 2019 · 10 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@lephix
Copy link

lephix commented Jan 9, 2019

I set the apiclient correctly, I can get pod, replace pod etc,.
But when I ran the example of exec and attach get following errors:

--> GET https://xxxx.com:6443/api/v1/namespaces/default/pods/plan-task-test-548756c754-4trnw/exec?stdin=true&stdout=true&stderr=true&tty=true&command=sh     HTTP/1.1
Sec-WebSocket-Protocol: v4.channel.k8s.io
User-Agent: Swagger-Codegen/1.0-SNAPSHOT/java
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: tCWA75OzR3YO6LlNj39xXg==
Sec-WebSocket-Version: 13
--> END GET
<-- HTTP/1.1 400 Bad Request (109ms)
Content-Type: application/json
Date: Wed, 09 Jan 2019 10:54:45 GMT
Content-Length: 234
OkHttp-Sent-Millis: 1547031285380
OkHttp-Received-Millis: 1547031285398
Exception in thread "OkHttp Dispatcher" java.lang.NullPointerException
	at com.squareup.okhttp.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.java:223)
	at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:232)
	at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:205)
	at com.squareup.okhttp.Call.access$100(Call.java:35)
	at com.squareup.okhttp.Call$AsyncCall.execute(Call.java:171)
	at com.squareup.okhttp.internal.NamedRunnable.run(NamedRunnable.java:33)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Anyone please help me to identify the problem.

@brendandburns
Copy link
Contributor

What version of the library are you running?

This looks like the same issue as #180 but that has been fixed...

@lephix
Copy link
Author

lephix commented Jan 11, 2019

@brendandburns I forgot to add the dependency info.

    <dependency>
        <groupId>io.kubernetes</groupId>
        <artifactId>client-java</artifactId>
        <version>3.0.0</version>
    </dependency>

@radhe-sravan
Copy link

@lephix is this resolved for you? I am facing the exact same issue with the same version of client library.

@lephix
Copy link
Author

lephix commented Feb 14, 2019

@radhe-sravan No. I am using fabric8 library for this func instead.

@zdf068
Copy link

zdf068 commented Mar 7, 2019

is this resolved for you? I have a same issue too

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 5, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 5, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ZhenghaeHo
Copy link

@lephix how did you resolved this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

7 participants