=== RUN TestFunctional/serial/StartWithProxy
functional_test.go:2230: (dbg) Run: out/minikube-darwin-amd64 start -p functional-040000 --memory=4000 --apiserver-port=8441 --wait=all --driver=hyperkit
functional_test.go:2230: (dbg) Non-zero exit: out/minikube-darwin-amd64 start -p functional-040000 --memory=4000 --apiserver-port=8441 --wait=all --driver=hyperkit : exit status 90 (15.056275736s)
-- stdout --
* [functional-040000] minikube v1.31.2 on Darwin 13.5.2
- MINIKUBE_LOCATION=17207
- KUBECONFIG=/Users/jenkins/minikube-integration/17207-1246/kubeconfig
- MINIKUBE_BIN=out/minikube-darwin-amd64
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- MINIKUBE_HOME=/Users/jenkins/minikube-integration/17207-1246/.minikube
- MINIKUBE_FORCE_SYSTEMD=
* Using the hyperkit driver based on user configuration
* Starting control plane node functional-040000 in cluster functional-040000
* Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
* Found network options:
- HTTP_PROXY=localhost:49786
* Please see https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/ for more details
-- /stdout --
** stderr **
! Local proxy ignored: not passing HTTP_PROXY=localhost:49786 to docker env.
! Local proxy ignored: not passing HTTP_PROXY=localhost:49786 to docker env.
! You appear to be using a proxy, but your NO_PROXY environment does not include the minikube IP (192.168.64.4).
X Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: sudo systemctl restart cri-docker.socket: Process exited with status 1
stdout:
stderr:
Job failed. See "journalctl -xe" for details.
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
** /stderr **
functional_test.go:2232: failed minikube start. args "out/minikube-darwin-amd64 start -p functional-040000 --memory=4000 --apiserver-port=8441 --wait=all --driver=hyperkit ": exit status 90
helpers_test.go:222: -----------------------post-mortem--------------------------------
helpers_test.go:239: (dbg) Run: out/minikube-darwin-amd64 status --format={{.Host}} -p functional-040000 -n functional-040000
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-darwin-amd64 status --format={{.Host}} -p functional-040000 -n functional-040000: exit status 6 (123.043748ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0910 13:58:08.357914 2121 status.go:415] kubeconfig endpoint: extract IP: "functional-040000" does not appear in /Users/jenkins/minikube-integration/17207-1246/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "functional-040000" host is not running, skipping log retrieval (state="Running\nWARNING: Your kubectl is pointing to stale minikube-vm.\nTo fix the kubectl context, run `minikube update-context`")
--- FAIL: TestFunctional/serial/StartWithProxy (15.18s)