=== RUN TestScheduledStopUnix
scheduled_stop_test.go:128: (dbg) Run: out/minikube-linux-amd64 start -p scheduled-stop-160518 --memory=2048 --driver=kvm2
E1128 03:05:23.023021 141240 cert_rotation.go:168] key failed with : open /home/jenkins/minikube-integration/17671-134061/.minikube/profiles/functional-414237/client.crt: no such file or directory
scheduled_stop_test.go:128: (dbg) Non-zero exit: out/minikube-linux-amd64 start -p scheduled-stop-160518 --memory=2048 --driver=kvm2 : exit status 90 (25.077529532s)
-- stdout --
* [scheduled-stop-160518] minikube v1.32.0 on Ubuntu 20.04 (kvm/amd64)
- MINIKUBE_LOCATION=17671
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- KUBECONFIG=/home/jenkins/minikube-integration/17671-134061/kubeconfig
- MINIKUBE_HOME=/home/jenkins/minikube-integration/17671-134061/.minikube
- MINIKUBE_BIN=out/minikube-linux-amd64
- MINIKUBE_FORCE_SYSTEMD=
* Using the kvm2 driver based on user configuration
* Starting control plane node scheduled-stop-160518 in cluster scheduled-stop-160518
* Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
-- /stdout --
** stderr **
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 **
scheduled_stop_test.go:130: starting minikube: exit status 90
-- stdout --
* [scheduled-stop-160518] minikube v1.32.0 on Ubuntu 20.04 (kvm/amd64)
- MINIKUBE_LOCATION=17671
- MINIKUBE_SUPPRESS_DOCKER_PERFORMANCE=true
- KUBECONFIG=/home/jenkins/minikube-integration/17671-134061/kubeconfig
- MINIKUBE_HOME=/home/jenkins/minikube-integration/17671-134061/.minikube
- MINIKUBE_BIN=out/minikube-linux-amd64
- MINIKUBE_FORCE_SYSTEMD=
* Using the kvm2 driver based on user configuration
* Starting control plane node scheduled-stop-160518 in cluster scheduled-stop-160518
* Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
-- /stdout --
** stderr **
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 **
panic.go:523: *** TestScheduledStopUnix FAILED at 2023-11-28 03:05:41.406920069 +0000 UTC m=+1805.956945056
helpers_test.go:222: -----------------------post-mortem--------------------------------
helpers_test.go:239: (dbg) Run:  out/minikube-linux-amd64 status --format={{.Host}} -p scheduled-stop-160518 -n scheduled-stop-160518
                                                
                                                helpers_test.go:239: (dbg) Non-zero exit: out/minikube-linux-amd64 status --format={{.Host}} -p scheduled-stop-160518 -n scheduled-stop-160518: exit status 6 (227.469297ms)
                                                
                                                -- stdout --
Running
WARNING: Your kubectl is pointing to stale minikube-vm.
To fix the kubectl context, run `minikube update-context`
-- /stdout --
** stderr **
E1128 03:05:41.619265 160378 status.go:415] kubeconfig endpoint: extract IP: "scheduled-stop-160518" does not appear in /home/jenkins/minikube-integration/17671-134061/kubeconfig
** /stderr **
helpers_test.go:239: status error: exit status 6 (may be ok)
helpers_test.go:241: "scheduled-stop-160518" 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`")
helpers_test.go:175: Cleaning up "scheduled-stop-160518" profile ...
helpers_test.go:178: (dbg) Run: out/minikube-linux-amd64 delete -p scheduled-stop-160518
--- FAIL: TestScheduledStopUnix (25.98s)