[
https://issues.apache.org/jira/browse/SPARK-34738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324165#comment-17324165
]
Attila Zsolt Piros commented on SPARK-34738:
--------------------------------------------
@shane I can modify my PR to skip the PV tests by just simply remove the k8s
label from it
https://github.com/apache/spark/blob/master/resource-managers/kubernetes/integration-tests/src/test/scala/org/apache/spark/deploy/k8s/integrationtest/PVTestsSuite.scala#L125
and
https://github.com/apache/spark/blob/master/resource-managers/kubernetes/integration-tests/src/test/scala/org/apache/spark/deploy/k8s/integrationtest/KubernetesSuite.scala#L567
As the tests are selected via that label, see the *-Dtest.include.tags=k8s* in
the mvn command:
{{+ /home/jenkins/workspace/SparkPullRequestBuilder-K8s/build/mvn install -f
/home/jenkins/workspace/SparkPullRequestBuilder-K8s/pom.xml -pl
resource-managers/kubernetes/integration-tests -am -Pscala-2.12 -Phadoop-3.2
-Pkubernetes -Pkubernetes-integration-tests -Djava.version=8
-Dspark.kubernetes.test.sparkTgz=/home/jenkins/workspace/SparkPullRequestBuilder-K8s/spark-3.2.0-SNAPSHOT-bin-20210408-a823d0e7c36.tgz
-Dspark.kubernetes.test.imageTag=N/A
-Dspark.kubernetes.test.imageRepo=docker.io/kubespark
-Dspark.kubernetes.test.deployMode=minikube -Dtest.include.tags=k8s
-Dspark.kubernetes.test.jvmImage=spark
-Dspark.kubernetes.test.pythonImage=spark-py
-Dspark.kubernetes.test.rImage=spark-r -Dlog4j.logger.org.apache.spark=DEBUG}}
I can use a different brand new label. This way if you can make the PR building
controlled by a text in the the PR title like it is done by maven version we
can switch on the test only for those PRs where we try to fix the problem.
Regarding:
> i could really use some help, and if it's useful, i can create some local
> accounts manually and allow ssh access for a couple of people to assist me.
I am happy to help I just need access to logs. As I told earlier it's probably
enough if the PR builder already uses Docker for testing and PV tests are
running. That was I referred to:
> This way I can run experiments via the PR builder and see the logs with my
> own eyes.
That way in my PR (or the next one) I can temporary can log out what I need.
But to be the safe side you can give me that ssh access too.
The only problem is time I can do the analizes part only at the end of next
week.
> Upgrade Minikube and kubernetes and move to docker 'virtualization' layer
> -------------------------------------------------------------------------
>
> Key: SPARK-34738
> URL: https://issues.apache.org/jira/browse/SPARK-34738
> Project: Spark
> Issue Type: Task
> Components: jenkins, Kubernetes
> Affects Versions: 3.2.0
> Reporter: Attila Zsolt Piros
> Assignee: Shane Knapp
> Priority: Major
> Attachments: integration-tests.log
>
>
> [~shaneknapp] as we discussed [on the mailing
> list|http://apache-spark-developers-list.1001551.n3.nabble.com/minikube-and-kubernetes-cluster-versions-for-integration-testing-td30856.html]
> Minikube can be upgraded to the latest (v1.18.1) and kubernetes version
> should be v1.17.3 (`minikube config set kubernetes-version v1.17.3`).
> [Here|https://github.com/apache/spark/pull/31829] is my PR which uses a new
> method to configure the kubernetes client. Thanks in advance to use it for
> testing on the Jenkins after the Minikube version is updated.
>
> Added by Shane:
> we also need to move from the kvm2 virtualization layer to docker. docker is
> a recommended driver w/the latest versions of minikube, and this will allow
> devs to more easily recreate the minikube/k8s env on their local workstations
> and run the integration tests in an identical environment as jenkins.
> the TL;DR is that upgrading to docker works, except that the PV integration
> tests are failing due to a couple of possible reasons:
> 1) the 'spark-kubernetes-driver' isn't properly being loaded
> (https://issues.apache.org/jira/browse/SPARK-34738?focusedCommentId=17312517&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17312517)
> 2) during the PV test run, the error message 'Given path
> (/opt/spark/pv-tests/tmp4595937990978494271.txt) does not exist' shows up in
> the logs. however, the mk cluster *does* mount successfully to the local
> bare-metal filesystem *and* if i 'minikube ssh' in to it, i can see the mount
> and read/write successfully to it
> (https://issues.apache.org/jira/browse/SPARK-34738?focusedCommentId=17312548&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17312548)
> i could really use some help, and if it's useful, i can create some local
> accounts manually and allow ssh access for a couple of people to assist me.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
