=== RUN TestNoKubernetes/serial/StartWithK8s
no_kubernetes_test.go:95: (dbg) Run: out/minikube-darwin-amd64 start -p NoKubernetes-20220630142805-16021 --driver=hyperkit
E0630 14:28:05.941917 16021 cert_rotation.go:168] key failed with : open /Users/jenkins/minikube-integration/darwin-amd64-hyperkit--14420-14815-b28e6de4ba37ffec66170588afce60c61d1bcd44/.minikube/profiles/auto-20220630141657-16021/client.crt: no such file or directory
=== CONT TestNoKubernetes/serial/StartWithK8s
no_kubernetes_test.go:95: (dbg) Non-zero exit: out/minikube-darwin-amd64 start -p NoKubernetes-20220630142805-16021 --driver=hyperkit : exit status 90 (1m1.027790956s)
-- stdout --
* [NoKubernetes-20220630142805-16021] minikube v1.26.0 on Darwin 12.4
- MINIKUBE_LOCATION=14420
- KUBECONFIG=/Users/jenkins/minikube-integration/darwin-amd64-hyperkit--14420-14815-b28e6de4ba37ffec66170588afce60c61d1bcd44/kubeconfig
- MINIKUBE_BIN=out/minikube-darwin-amd64
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- MINIKUBE_HOME=/Users/jenkins/minikube-integration/darwin-amd64-hyperkit--14420-14815-b28e6de4ba37ffec66170588afce60c61d1bcd44/.minikube
* Using the hyperkit driver based on user configuration
* Starting control plane node NoKubernetes-20220630142805-16021 in cluster NoKubernetes-20220630142805-16021
* Creating hyperkit VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
-- /stdout --
** stderr **
X Exiting due to RUNTIME_ENABLE: Temporary Error: sudo crictl version: Process exited with status 1
stdout:
stderr:
time="2022-06-30T21:29:06Z" level=fatal msg="connect: connect endpoint 'unix:///var/run/cri-dockerd.sock', make sure you are running as root and the endpoint has been started: context deadline exceeded"
*
╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ * 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 **
no_kubernetes_test.go:97: failed to start minikube with args: "out/minikube-darwin-amd64 start -p NoKubernetes-20220630142805-16021 --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 NoKubernetes-20220630142805-16021 -n NoKubernetes-20220630142805-16021
helpers_test.go:239: (dbg) Non-zero exit: out/minikube-darwin-amd64 status --format={{.Host}} -p NoKubernetes-20220630142805-16021 -n NoKubernetes-20220630142805-16021: exit status 6 (133.255884ms)
-- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E0630 14:29:06.719022 23213 status.go:413] kubeconfig endpoint: extract IP: "NoKubernetes-20220630142805-16021" does not appear in /Users/jenkins/minikube-integration/darwin-amd64-hyperkit--14420-14815-b28e6de4ba37ffec66170588afce60c61d1bcd44/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "NoKubernetes-20220630142805-16021" 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: TestNoKubernetes/serial/StartWithK8s (61.16s)