Skip to content

kvm2: minikube network does not exist #3636

Closed
@rnmhdn

Description

@rnmhdn

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.33.1

  • OS (e.g. from /etc/os-release): Linux 4.20.6-arch1-1-ARCH Need a reliable and low latency local cluster setup for Kubernetes  #1 SMP PREEMPT Thu Jan 31 08:22:01 UTC 2019 x86_64 GNU/Linux
  • VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): "DriverName": "kvm2",
  • ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): "Boot2DockerURL": "file:///home/aran/.minikube/cache/iso/minikube-v0.33.1.iso",
    "ISO": "/home/aran/.minikube/machines/minikube/boot2docker.iso"
$ minikube ssh cat /etc/VERSION
E0207 22:36:29.854750    2550 ssh.go:54] Error attempting to ssh/run-ssh-command: Error getting state of host: getting connection: looking up domain: virError(Code=42, Domain=10, Message='Domain not found: no domain with matching name 'minikube'')
  • Install tools:
  • Others:
    The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver:"; 
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json

What happened:
minikube network does not exist
What you expected to happen:
minikube network exists.
How to reproduce it (as minimally and precisely as possible):

    torify curl -LO https://storage.googleapis.com/kubernetes-release/release/$(torify curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x ./kubectl && sudo mv ./kubectl /usr/local/bin/kubectl 
    torify curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.33.1/minikube-darwin-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
    sudo pacman -Sy libvirt qemu-headless ebtables dnsmasq 
    sudo systemctl enable libvirtd.service
    sudo pacman -Sy docker-machine
    installed minikube-bin kubectl-bin docker-machine-driver-kvm2 from AUR
    sudo pacman -S dmidecode
    sudo usermod -aG libvirt aran
    sudo reboot 
    torify wget "https://storage.googleapis.com/minikube/iso/minikube-v0.33.1.iso"
    python -m http.server

Output of minikube logs (if applicable):

F0207 22:45:38.784909    3156 logs.go:50] Error getting cluster bootstrapper: getting kubeadm bootstrapper: getting ssh client: Error creating new ssh host from driver: Error getting ssh host name for driver: machine in unknown state: getting connection: looking up domain: virError(Code=42, Domain=10, Message='Domain not found: no domain with matching name 'minikube'')

Anything else do we need to know:

$ sudo virsh net-list --all Name      State    Autostart   Persistent
--------------------------------------------
 default   active   no          yes

**Update: **
I removed .minikube and restarted libvirtd and ran the command again and now I get:
virError(Code=9, Domain=20, Message='operation failed: domain 'minikube' already exists with uuid f718bd7b-3f63-4151-a89d-02cca2a39c9b')
**Update: **
I did minikube delete
and then:

$ minikube start --iso-url "http://localhost:8000/minikube-v0.33.1.iso" --vm-driver kvm2
Starting local Kubernetes v1.13.2 cluster...
Starting VM...

and it's stuck there.
here is the last msgs in my journal:

Feb 07 23:11:43 Christopher audit[606]: VIRT_RESOURCE pid=606 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm resrc=vcpu reason=start vm="minikube" uuid=6130b1e6-5c16-454c-93ca-b6c46edfbf70 old-vcpu=0 new-vcpu=2 exe="/usr/bin/libvirtd" hostname=? addr=? terminal=? res=success'
Feb 07 23:11:43 Christopher audit[606]: VIRT_CONTROL pid=606 uid=0 auid=4294967295 ses=4294967295 msg='virt=kvm op=start reason=booted vm="minikube" uuid=6130b1e6-5c16-454c-93ca-b6c46edfbf70 vm-pid=2910 exe="/usr/bin/libvirtd" hostname=? addr=? terminal=? res=success'
Feb 07 23:11:45 Christopher kernel: virbr1: port 2(vnet1) entered learning state
Feb 07 23:11:45 Christopher kernel: virbr0: port 2(vnet0) entered learning state
Feb 07 23:11:47 Christopher NetworkManager[592]: <info>  [1549568507.1642] device (virbr0): carrier: link connected
Feb 07 23:11:47 Christopher NetworkManager[592]: <info>  [1549568507.1644] device (virbr1): carrier: link connected
Feb 07 23:11:47 Christopher kernel: virbr0: port 2(vnet0) entered forwarding state
Feb 07 23:11:47 Christopher kernel: virbr0: topology change detected, propagating
Feb 07 23:11:47 Christopher kernel: virbr1: port 2(vnet1) entered forwarding state
Feb 07 23:11:47 Christopher kernel: virbr1: topology change detected, propagating
Feb 07 23:12:08 Christopher dnsmasq-dhcp[696]: DHCPDISCOVER(virbr0) 6c:66:db:0f:21:13
Feb 07 23:12:08 Christopher dnsmasq-dhcp[696]: DHCPOFFER(virbr0) 192.168.122.215 6c:66:db:0f:21:13
Feb 07 23:12:08 Christopher dnsmasq-dhcp[696]: DHCPDISCOVER(virbr0) 6c:66:db:0f:21:13
Feb 07 23:12:08 Christopher dnsmasq-dhcp[696]: DHCPOFFER(virbr0) 192.168.122.215 6c:66:db:0f:21:13
Feb 07 23:12:08 Christopher dnsmasq-dhcp[696]: DHCPREQUEST(virbr0) 192.168.122.215 6c:66:db:0f:21:13
Feb 07 23:12:08 Christopher dnsmasq-dhcp[696]: DHCPACK(virbr0) 192.168.122.215 6c:66:db:0f:21:13 minikube
Feb 07 23:12:08 Christopher dnsmasq-dhcp[2899]: DHCPDISCOVER(virbr1) 70:8a:20:5b:bf:09
Feb 07 23:12:08 Christopher dnsmasq-dhcp[2899]: DHCPOFFER(virbr1) 192.168.39.44 70:8a:20:5b:bf:09
Feb 07 23:12:08 Christopher dnsmasq-dhcp[2899]: DHCPDISCOVER(virbr1) 70:8a:20:5b:bf:09
Feb 07 23:12:08 Christopher dnsmasq-dhcp[2899]: DHCPOFFER(virbr1) 192.168.39.44 70:8a:20:5b:bf:09
Feb 07 23:12:08 Christopher dnsmasq-dhcp[2899]: DHCPREQUEST(virbr1) 192.168.39.44 70:8a:20:5b:bf:09
Feb 07 23:12:08 Christopher dnsmasq-dhcp[2899]: DHCPACK(virbr1) 192.168.39.44 70:8a:20:5b:bf:09 minikube

Metadata

Metadata

Assignees

No one assigned

    Labels

    co/kvm2-driverKVM2 driver related issueshelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugCategorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.priority/backlogHigher priority than priority/awaiting-more-evidence.r/2019q2Issue was last reviewed 2019q2

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions