minikube: kvm2 1.3.0 regression: Error dialing tcp via ssh client: dial tcp :22: connect: connection refused
The exact command to reproduce the issue:
minikube start --vm-driver kvm2
The full output of the command that failed:
😄 minikube v1.3.0 on Ubuntu 18.04
🔥 Creating kvm2 VM (CPUs=8, Memory=12288MB, Disk=20000MB) ...
E0807 14:34:18.549366 23184 start.go:723] StartHost: create: Error creating machine: Error in driver during machine creation: machine didn't return an IP after 120 seconds
💣 Unable to start VM: create: Error creating machine: Error in driver during machine creation: machine didn't return an IP after 120 seconds
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose
💣 disable failed: [command runner: getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp :22: connect: connection refused]
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose
ssh: dial tcp :22: connect: connection refused
The output of the minikube logs command:
💣 command runner: getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp :22: connect: connection refused
The operating system version:
Ubuntu 18.04, running kernel 5.0.0-23-generic.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 20 (7 by maintainers)
@medyagh so, after
git bisecting everything, including the disk image (thanks, contributor documentation!), I just couldn’t find a bad commit! It turns out there was something weird with the 1.3.0 ISO in my disk. Apparently, the cached ISO was corrupt. I cleaned the cache and voi la! It works again!I’m closing this. Thanks, guys.
Update: got the
virt-host-validateto pass by adding the user to groupkvm. Minikube, however, still fails.When I have the time to do so, I will
git bisectthis.Got it. I will provide the requested data tomorrow.
Thanks!