spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stavros Kontopoulos (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SPARK-26997) k8s integration tests failing after client upgraded to 4.1.2
Date Tue, 26 Feb 2019 21:29:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-26997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778557#comment-16778557
] 

Stavros Kontopoulos edited comment on SPARK-26997 at 2/26/19 9:28 PM:
----------------------------------------------------------------------

[~vanzin] I run the tests successfully with the latest minikube version (v0.34.1) and k8s
1.13.3. It seems like a compatibility issue AFAIK. I have seen the failures in our intern
ci as well. 

There is a compatibility matrix for the fabric8io client here: [https://github.com/fabric8io/kubernetes-client/blob/8b85c5f7259c86069a9ab591f31c91cd4fb88d86/README.md#compatibility-matrix] but
does not contain version v4.1.2 yet.

[~shaneknapp] one problem though (just as a continuation of the discussion about testing)
is that while in theory using something like ` --kubernetes-version=v1.11.7`  should work
for targeting any k8s version it didnt. It failed for this case with: `Caused by: java.net.UnknownHostException:
kubernetes.default.svc: for me. I am trying to make tests pass for [https://github.com/apache/spark/pull/23514] while
also checking against versions that are still being patched or are still supported. Moreover,
as a side note one reason I have also used `driver=none` is because on aws instances you cant
run kvm, so it was not only for avoiding using a vm (of course security is a big issue with
that but not if you are doing it on an isolated host).

 


was (Author: skonto):
[~vanzin] I run the tests successfully with the latest minikube version (v0.34.1) and k8s
1.13.3. It seems like a compatibility issue AFAIK. I have seen the failures in our intern
ci as well. 

There is a compatibility matrix for the fabric8io client here: [https://github.com/fabric8io/kubernetes-client/blob/8b85c5f7259c86069a9ab591f31c91cd4fb88d86/README.md#compatibility-matrix] but
does not contain version v4.1.2 yet.

[~shaneknapp] one problem though (just as a continuation of the discussion about testing)
is that while in theory using something like ` --kubernetes-version=v1.11.7`  should work
for targeting any k8s version it didnt. It failed for this case with: `Caused by: java.net.UnknownHostException:
kubernetes.default.svc: for me. I am trying to make tests pass for [https://github.com/apache/spark/pull/23514] while
also checking against versions that are still being patched or are still supported. Moreover,
as a side note one reason I have also used `driver=none` is because on aws instances you cant
run kvm, so it was not only for avoiding using a vm.

 

> k8s integration tests failing after client upgraded to 4.1.2
> ------------------------------------------------------------
>
>                 Key: SPARK-26997
>                 URL: https://issues.apache.org/jira/browse/SPARK-26997
>             Project: Spark
>          Issue Type: Bug
>          Components: Kubernetes
>    Affects Versions: 3.0.0
>            Reporter: Marcelo Vanzin
>            Priority: Critical
>
> SPARK-26742 upgraded the client libs to version 4.1.2, and that doesn't seem to agree
well with the minikube we're using in jenkins. My PRs are failing (minikube 0.25):
> {noformat}
> 19/02/25 17:46:52.599 ScalaTest-main-running-KubernetesSuite INFO ProcessUtils: 19/02/25
17:46:52 INFO ShutdownHookManager: Deleting directory /tmp/spark-3007689c-e3ca-48f5-a673-f3bad5c4774a
> 19/02/25 17:46:52.788 OkHttp https://192.168.39.69:8443/... ERROR ExecWebSocketListener:
Exec Failure: HTTP:500. Message:container not found ("spark-kubernetes-driver")
> java.net.ProtocolException: Expected HTTP 101 response but was '500 Internal Server Error'
> 	at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229)
> 	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196)
> 	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
> 	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 	at java.lang.Thread.run(Thread.java:748)
> 19/02/25 17:46:52.999 OkHttp https://192.168.39.69:8443/... ERROR ExecWebSocketListener:
Exec Failure: HTTP:404. Message:404 page not found
> java.net.ProtocolException: Expected HTTP 101 response but was '404 Not Found'
> 	at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229)
> 	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196)
> 	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
> 	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 	at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Tests pass on my local minikube (0.34). Reverting that change makes them pass on jenkins
(see https://github.com/apache/spark/pull/23893).
> Not sure if this is a client bug or a compatibility issue.
> [~shaneknapp] [~skonto]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message