FailedConsole Output

Started by upstream project "spark-branch-2.3-k8s-make-spark-distribution" build number 440
originally caused by:
 Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on research-jenkins-worker-08 (ubuntu research-08) in workspace /home/jenkins/workspace/spark-branch-2.3-k8s-spark-integration
[WS-CLEANUP] Deleting project workspace...
Cloning the remote Git repository
Cloning repository
 > git init /home/jenkins/workspace/spark-branch-2.3-k8s-spark-integration # timeout=10
Fetching upstream changes from
 > git --version # timeout=10
 > git fetch --tags --progress +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url # timeout=10
Fetching upstream changes from
 > git fetch --tags --progress +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision bcecb08879131aaa490c5ef711959ab04cda3b0e (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f bcecb08879131aaa490c5ef711959ab04cda3b0e
 > git rev-list bcecb08879131aaa490c5ef711959ab04cda3b0e # timeout=10
Copied 1 artifact from "spark-branch-2.3-k8s-make-spark-distribution" build number 440
[spark-branch-2.3-k8s-spark-integration] $ /bin/bash /tmp/
There is a newer version of minikube available (v1.1.1).  Download it here:

To disable this notification, run the following:
minikube config set WantUpdateNotification false
o   minikube v0.34.1 on linux (amd64)
i   Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
:   Restarting existing kvm2 VM for "minikube" ...
:   Waiting for SSH access ...
-   "minikube" IP address is
-   Configuring Docker as the container runtime ...
-   Preparing Kubernetes environment ...
-   Pulling images required by Kubernetes v1.13.3 ...
:   Relaunching Kubernetes v1.13.3 using kubeadm ... 
:   Waiting for kube-proxy to come back up ...
-   Verifying component health ......
+   kubectl is now configured to use "minikube"
=   Done! Thank you for using minikube!
-   Mounting /tmp/tmp.n3NFGMvEAg into /tmp/tmp.n3NFGMvEAg on the minikube VM
*   This daemon process needs to stay alive for the mount to be accessible ...
ufs starting
Error from server (AlreadyExists): "serviceaccounts-cluster-admin" already exists
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-readable POM /home/jenkins/workspace/spark-branch-2.3-k8s-spark-integration/integration-test/pom.xml: /home/jenkins/workspace/spark-branch-2.3-k8s-spark-integration/integration-test/pom.xml (No such file or directory) @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   The project  (/home/jenkins/workspace/spark-branch-2.3-k8s-spark-integration/integration-test/pom.xml) has 1 error
[ERROR]     Non-readable POM /home/jenkins/workspace/spark-branch-2.3-k8s-spark-integration/integration-test/pom.xml: /home/jenkins/workspace/spark-branch-2.3-k8s-spark-integration/integration-test/pom.xml (No such file or directory)
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]
:   Stopping "minikube" in kvm2 ...
-   "minikube" stopped.
/tmp/ line 46:  1020 Killed                  minikube mount ${PVC_TESTS_HOST_PATH}:${PVC_TESTS_VM_PATH} --9p-version=9p2000.L --gid=0 --uid=185
Build step 'Execute shell' marked build as failure
Finished: FAILURE