Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

minikube deletes custom network passed in via --kvm-network #3581

Closed
malcolm061990 opened this issue Jan 24, 2019 · 9 comments
Closed

minikube deletes custom network passed in via --kvm-network #3581

malcolm061990 opened this issue Jan 24, 2019 · 9 comments
Labels
co/kvm2-driver KVM2 driver related issues good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/backlog Higher priority than priority/awaiting-more-evidence. r/2019q2 Issue was last reviewed 2019q2

Comments

@malcolm061990
Copy link

BUG REPORT

Minikube version: 0.33.1

  • OS: Ubuntu 18.04.1 LTS (Bionic Beaver)
  • VM Driver : kvm2
  • ISO version: minikube-v0.33.1.iso

What happened:
Hangs at Starting cluster components...

What you expected to happen:
Starting cluster without hangs and errors

How to reproduce it (as minimally and precisely as possible):

minikube start \
	--cpus=4 \
	--memory=18000 \
	--insecure-registry=192.168.99.1:5000  \
	--vm-driver=kvm2 \
	--disk-size=30g \
	--kvm-network=minikube-net \
	--kubernetes-version=v1.9.11 \
	--extra-config=apiserver.authorization-mode=RBAC;

Output of minikube logs (if applicable):
I give only small part of the log because the log is huge

Jan 24 12:16:10 minikube kubelet[2529]: E0124 12:16:10.805011    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:11 minikube kubelet[2529]: E0124 12:16:11.803974    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:11 minikube kubelet[2529]: E0124 12:16:11.805112    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:11 minikube kubelet[2529]: E0124 12:16:11.805820    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:12 minikube kubelet[2529]: I0124 12:16:12.140210    2529 kubelet_node_status.go:273] Setting node annotation to enable volume controller attach/detach
Jan 24 12:16:12 minikube kubelet[2529]: W0124 12:16:12.140675    2529 kubelet_node_status.go:977] Failed to set some node status fields: can't get ip address of node minikube. error: No default routes.
Jan 24 12:16:12 minikube kubelet[2529]: I0124 12:16:12.141217    2529 kubelet_node_status.go:273] Setting node annotation to enable volume controller attach/detach
Jan 24 12:16:12 minikube kubelet[2529]: W0124 12:16:12.141726    2529 kubelet_node_status.go:977] Failed to set some node status fields: can't get ip address of node minikube. error: No default routes.
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.444127    2529 dns.go:131] Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 8.8.8.8 8.8.4.4 2001:4860:4860::8888
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.444467    2529 dns.go:131] Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 8.8.8.8 8.8.4.4 2001:4860:4860::8888
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449349    2529 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449398    2529 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "kube-scheduler-minikube_kube-system(4def8cb5c301cb9153f093be762145ac)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449424    2529 kuberuntime_manager.go:647] createPodSandbox for pod "kube-scheduler-minikube_kube-system(4def8cb5c301cb9153f093be762145ac)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449495    2529 pod_workers.go:186] Error syncing pod 4def8cb5c301cb9153f093be762145ac ("kube-scheduler-minikube_kube-system(4def8cb5c301cb9153f093be762145ac)"), skipping: failed to "CreatePodSandbox" for "kube-scheduler-minikube_kube-system(4def8cb5c301cb9153f093be762145ac)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-scheduler-minikube_kube-system(4def8cb5c301cb9153f093be762145ac)\" failed: rpc error: code = Unknown desc = failed pulling image \"gcr.io/google_containers/pause-amd64:3.0\": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable"
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449706    2529 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449760    2529 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "kube-addon-manager-minikube_kube-system(0f5415e29ffead838972d3981903fcf7)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449784    2529 kuberuntime_manager.go:647] createPodSandbox for pod "kube-addon-manager-minikube_kube-system(0f5415e29ffead838972d3981903fcf7)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.449873    2529 pod_workers.go:186] Error syncing pod 0f5415e29ffead838972d3981903fcf7 ("kube-addon-manager-minikube_kube-system(0f5415e29ffead838972d3981903fcf7)"), skipping: failed to "CreatePodSandbox" for "kube-addon-manager-minikube_kube-system(0f5415e29ffead838972d3981903fcf7)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-addon-manager-minikube_kube-system(0f5415e29ffead838972d3981903fcf7)\" failed: rpc error: code = Unknown desc = failed pulling image \"gcr.io/google_containers/pause-amd64:3.0\": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable"
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.804966    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.806020    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:12 minikube kubelet[2529]: E0124 12:16:12.807010    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:13 minikube kubelet[2529]: E0124 12:16:13.805951    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:13 minikube kubelet[2529]: E0124 12:16:13.807400    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:13 minikube kubelet[2529]: E0124 12:16:13.807821    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:14 minikube kubelet[2529]: E0124 12:16:14.806818    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:14 minikube kubelet[2529]: E0124 12:16:14.808177    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:14 minikube kubelet[2529]: E0124 12:16:14.809164    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:15 minikube kubelet[2529]: E0124 12:16:15.807689    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:15 minikube kubelet[2529]: E0124 12:16:15.809077    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:15 minikube kubelet[2529]: E0124 12:16:15.809811    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:16 minikube kubelet[2529]: I0124 12:16:16.140158    2529 kubelet_node_status.go:273] Setting node annotation to enable volume controller attach/detach
Jan 24 12:16:16 minikube kubelet[2529]: W0124 12:16:16.140655    2529 kubelet_node_status.go:977] Failed to set some node status fields: can't get ip address of node minikube. error: No default routes.
Jan 24 12:16:16 minikube kubelet[2529]: I0124 12:16:16.285546    2529 kubelet_node_status.go:273] Setting node annotation to enable volume controller attach/detach
Jan 24 12:16:16 minikube kubelet[2529]: W0124 12:16:16.285963    2529 kubelet_node_status.go:977] Failed to set some node status fields: can't get ip address of node minikube. error: No default routes.
Jan 24 12:16:16 minikube kubelet[2529]: I0124 12:16:16.289121    2529 kubelet_node_status.go:82] Attempting to register node minikube
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.289704    2529 kubelet_node_status.go:106] Unable to register node "minikube" with API server: Post https://192.168.39.247:8443/api/v1/nodes: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.444391    2529 dns.go:131] Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 8.8.8.8 8.8.4.4 2001:4860:4860::8888
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.448531    2529 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.448690    2529 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "kube-apiserver-minikube_kube-system(0dce604f5c0e40c5637e08418c55f676)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.448723    2529 kuberuntime_manager.go:647] createPodSandbox for pod "kube-apiserver-minikube_kube-system(0dce604f5c0e40c5637e08418c55f676)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.448801    2529 pod_workers.go:186] Error syncing pod 0dce604f5c0e40c5637e08418c55f676 ("kube-apiserver-minikube_kube-system(0dce604f5c0e40c5637e08418c55f676)"), skipping: failed to "CreatePodSandbox" for "kube-apiserver-minikube_kube-system(0dce604f5c0e40c5637e08418c55f676)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-apiserver-minikube_kube-system(0dce604f5c0e40c5637e08418c55f676)\" failed: rpc error: code = Unknown desc = failed pulling image \"gcr.io/google_containers/pause-amd64:3.0\": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable"
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.808681    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.810266    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:16 minikube kubelet[2529]: E0124 12:16:16.810910    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:17 minikube kubelet[2529]: E0124 12:16:17.809869    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:17 minikube kubelet[2529]: E0124 12:16:17.811036    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:17 minikube kubelet[2529]: E0124 12:16:17.812185    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:18 minikube kubelet[2529]: I0124 12:16:18.140125    2529 kubelet_node_status.go:273] Setting node annotation to enable volume controller attach/detach
Jan 24 12:16:18 minikube kubelet[2529]: W0124 12:16:18.140521    2529 kubelet_node_status.go:977] Failed to set some node status fields: can't get ip address of node minikube. error: No default routes.
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.444487    2529 dns.go:131] Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 8.8.8.8 8.8.4.4 2001:4860:4860::8888
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.449865    2529 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.449938    2529 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "kube-controller-manager-minikube_kube-system(a7622f9e283b680c5921f80d152bdd7d)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.449965    2529 kuberuntime_manager.go:647] createPodSandbox for pod "kube-controller-manager-minikube_kube-system(a7622f9e283b680c5921f80d152bdd7d)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.450062    2529 pod_workers.go:186] Error syncing pod a7622f9e283b680c5921f80d152bdd7d ("kube-controller-manager-minikube_kube-system(a7622f9e283b680c5921f80d152bdd7d)"), skipping: failed to "CreatePodSandbox" for "kube-controller-manager-minikube_kube-system(a7622f9e283b680c5921f80d152bdd7d)" with CreatePodSandboxError: "CreatePodSandbox for pod \"kube-controller-manager-minikube_kube-system(a7622f9e283b680c5921f80d152bdd7d)\" failed: rpc error: code = Unknown desc = failed pulling image \"gcr.io/google_containers/pause-amd64:3.0\": Error response from daemon: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable"
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.810765    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.39.247:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.811865    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:473: Failed to list *v1.Service: Get https://192.168.39.247:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused
Jan 24 12:16:18 minikube kubelet[2529]: E0124 12:16:18.812930    2529 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:482: Failed to list *v1.Node: Get https://192.168.39.247:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 192.168.39.247:8443: getsockopt: connection refused

Anything else do we need to know:
Some days ago I could start minikube without problems using 0.27.0 version. I wanted to upgrade it. After upgrade to 0.33.1 this error appeared. Returning to 0.27.0 caused the error too.
I delete the minikube cluster using this:
minikube stop && minikube delete && rm -rf ~/.minikube

The network "minikube-net" was created earlier by virsh net-create ./minikube/minikube-kvm-network.xml
The content of minikube-kvm-network.xml:

<network>
	<name>minikube-net</name>
	<bridge name="virbr100" />
	<forward mode="nat" />
	<ip address="192.168.99.1" netmask="255.255.255.0">
		<dhcp>
			<range start="192.168.99.100" end="192.168.99.100"/>
		</dhcp>
	</ip>
</network>
@malcolm061990
Copy link
Author

I killed half of day with this situation.
I found out that when I deleted the minikube cluster the kvm network (which I created separately with virsh net-create) was deleted too! And when I started minikube (after deleting) it created some custom network 192.168.39.0/24
It's very strange behavior.
Why does minikube delete the network that is created separately from minikube? May be I want to use this network for some other virtual machines or services...

@tstromberg tstromberg changed the title Hung at "Starting cluster components..." kvm2: Hung at "Starting cluster components..." - connect: network is unreachable Jan 24, 2019
@tstromberg
Copy link
Contributor

It seems reasonable that if you pass in --kvm-network=minikube-net - that it should not remove the network. I'd be happy to help review any PR which addresses this. Help wanted!

@tstromberg tstromberg changed the title kvm2: Hung at "Starting cluster components..." - connect: network is unreachable minikube deletes network passed in via --kvm-network Jan 24, 2019
@tstromberg tstromberg added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. co/kvm2-driver KVM2 driver related issues good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Jan 24, 2019
@tstromberg tstromberg changed the title minikube deletes network passed in via --kvm-network minikube deletes custom network passed in via --kvm-network Jan 24, 2019
@tstromberg tstromberg added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Jan 24, 2019
@malcolm061990
Copy link
Author

It seems reasonable that if you pass in --kvm-network=minikube-net - that it should not remove the network. I'd be happy to help review any PR which addresses this. Help wanted!

Yes, it should not remove the network but it removes :(
What is PR?

@afbjorklund
Copy link
Collaborator

Minikube will create the private network (if it doesn't exist), so seems reasonable it should destroy it.

But when you pass in a custom network, it would probably be a good idea to disable this feature...

Maybe add a boolean to signal if we created it ?

And then skipping over destroying it, if we didn't ?

@malcolm061990
Copy link
Author

Maybe add a boolean to signal if we created it ?
And then skipping over destroying it, if we didn't ?

Yes, you can add boolean to signal who creates the network. But I think the default behavior must be NOT to delete the custom network.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 8, 2019
@malcolm061990
Copy link
Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 10, 2019
@josedonizetti
Copy link
Member

josedonizetti commented May 21, 2019 •
edited
Loading

Hey, took some time to look into this issue. One thing I noticed is that minikube already doesn't delete the network passed with the option --kvm-network. It ignores it, cos it considers it is managed by the OS.
https://github.com/kubernetes/minikube/blob/master/pkg/drivers/kvm/network.go#L168

As @afbjorklund commented it does delete the Private Network, which isn't the same thing as the option --kvm-network: https://github.com/kubernetes/minikube/blob/master/pkg/minikube/drivers/kvm2/driver.go#L67

What I think happened in this case it that the network @malcolm061990 created actually had the same name (look on the XML he posted -> minikube-net) of the private network that minikube creates https://github.com/kubernetes/minikube/blob/master/pkg/minikube/drivers/kvm2/driver.go#L68, so due to the conflict it ends up been deleted.

@tstromberg tstromberg added the r/2019q2 Issue was last reviewed 2019q2 label May 22, 2019
@josedonizetti josedonizetti mentioned this issue May 30, 2019
Merged
medyagh pushed a commit that referenced this issue Jun 15, 2019
@josedonizetti @medyagh
Add kvm network name validation
a2d844e 
closes for #3581
@malcolm061990
Copy link
Author

Hey, took some time to look into this issue. One thing I noticed is that minikube already doesn't delete the network passed with the option --kvm-network. It ignores it, cos it considers it is managed by the OS.
https://github.com/kubernetes/minikube/blob/master/pkg/drivers/kvm/network.go#L168

As @afbjorklund commented it does delete the Private Network, which isn't the same thing as the option --kvm-network: https://github.com/kubernetes/minikube/blob/master/pkg/minikube/drivers/kvm2/driver.go#L67

What I think happened in this case it that the network @malcolm061990 created actually had the same name (look on the XML he posted -> minikube-net) of the private network that minikube creates https://github.com/kubernetes/minikube/blob/master/pkg/minikube/drivers/kvm2/driver.go#L68, so due to the conflict it ends up been deleted.

Thanks!
Cool!
I didn't know that my custom network name is the same as minikube's :)

@josedonizetti josedonizetti mentioned this issue Jul 2, 2019
Closed
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/kvm2-driver KVM2 driver related issues good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/backlog Higher priority than priority/awaiting-more-evidence. r/2019q2 Issue was last reviewed 2019q2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@josedonizetti @tstromberg @afbjorklund @k8s-ci-robot @malcolm061990 @fejta-bot