<p>I'm currently dealing with this situation.</p>
<p>Whenever I create multi-node cluster using Minikube, when I stop it and restart it again. It will lose track of the &quot;middle&quot; nodes, e.g. I create 4 nodes: <code>m1</code>, <code>m2</code>, <code>m3</code>, <code>m4</code>; by some reason Minikube loses track of <code>m2</code> and <code>m3</code>.</p>
<p><strong>Scenario:</strong></p>
<p>Let's say I want to create a Kubernetes cluster with Vault, so then I create one a profile named &quot;vault-cluster&quot; with 4 nodes (1 control plane and 3 worker nodes):</p>
<pre><code>$ minikube start --nodes 4 -p vault-cluster
</code></pre>
<p>Then when I stop them using:</p>
<pre><code>minikube stop -p vault-cluster
</code></pre>
<p><strong>Expected behaviour:</strong></p>
<p><strong>Output:</strong></p>
<pre><code>✋  Stopping node &quot;vault-cluster&quot;  ...
✋  Stopping node &quot;vault-cluster-m02&quot;  ...
✋  Stopping node &quot;vault-cluster-m03&quot;  ...
✋  Stopping node &quot;vault-cluster-m04&quot;  ...
🛑  4 nodes stopped.
</code></pre>
<p>So when when I started again:</p>
<p><strong>Output:</strong></p>
<pre><code>$ minikube start -p vault-cluster
😄  [vault-cluster] minikube v1.20.0 on Microsoft Windows 10 Pro 10.0.19042 Build 19042
✨  Using the virtualbox driver based on existing profile
🎉  minikube 1.21.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.21.0
💡  To disable this notice, run: 'minikube config set WantUpdateNotification false'

👍  Starting control plane node vault-cluster in cluster vault-cluster
🔄  Restarting existing virtualbox VM for &quot;vault-cluster&quot; ...
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
🔗  Configuring CNI (Container Networking Interface) ...
🔎  Verifying Kubernetes components...
    ▪ Using image kubernetesui/dashboard:v2.1.0
    ▪ Using image kubernetesui/metrics-scraper:v1.0.4
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
👍  Starting node vault-cluster-m02 in cluster vault-cluster
🔄  Restarting existing virtualbox VM for &quot;vault-cluster-m02&quot; ...
🌐  Found network options:
    ▪ NO_PROXY=192.168.99.120
    ▪ no_proxy=192.168.99.120
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
    ▪ env NO_PROXY=192.168.99.120
🔎  Verifying Kubernetes components...
👍  Starting node vault-cluster-m03 in cluster vault-cluster
🔄  Restarting existing virtualbox VM for &quot;vault-cluster-m03&quot; ...
🌐  Found network options:
    ▪ NO_PROXY=192.168.99.120,192.168.99.121
    ▪ no_proxy=192.168.99.120,192.168.99.121
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
    ▪ env NO_PROXY=192.168.99.120
    ▪ env NO_PROXY=192.168.99.120,192.168.99.121
🔎  Verifying Kubernetes components...
👍  Starting node vault-cluster-m04 in cluster vault-cluster
🔄  Restarting existing virtualbox VM for &quot;vault-cluster-m04&quot; ...
🌐  Found network options:
    ▪ NO_PROXY=192.168.99.120,192.168.99.121,192.168.99.122
    ▪ no_proxy=192.168.99.120,192.168.99.121,192.168.99.122
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
    ▪ env NO_PROXY=192.168.99.120
    ▪ env NO_PROXY=192.168.99.120,192.168.99.121
    ▪ env NO_PROXY=192.168.99.120,192.168.99.121,192.168.99.122
🔎  Verifying Kubernetes components...
🏄  Done! kubectl is now configured to use &quot;vault-cluster&quot; cluster and &quot;default&quot; namespace by default
</code></pre>
<p><strong>ACTUAL BEHAVIOUR:</strong></p>
<pre><code>$ minikube stop -p vault-cluster
✋  Stopping node &quot;vault-cluster&quot;  ...
✋  Stopping node &quot;vault-cluster-m04&quot;  ...
✋  Stopping node &quot;vault-cluster-m04&quot;  ...
✋  Stopping node &quot;vault-cluster-m04&quot;  ...
</code></pre>
<p>So when this is what happens when I try to start cluster again:</p>
<pre><code>$ minikube start -p vault-cluster
😄  [vault-cluster] minikube v1.20.0 on Microsoft Windows 10 Pro 10.0.19042 Build 19042
✨  Using the virtualbox driver based on existing profile
👍  Starting control plane node vault-cluster in cluster vault-cluster
🔄  Restarting existing virtualbox VM for &quot;vault-cluster&quot; ...
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
🔗  Configuring CNI (Container Networking Interface) ...
🔎  Verifying Kubernetes components...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
    ▪ Using image kubernetesui/metrics-scraper:v1.0.4
    ▪ Using image kubernetesui/dashboard:v2.1.0
🌟  Enabled addons: default-storageclass, dashboard
👍  Starting node vault-cluster-m04 in cluster vault-cluster
🔄  Restarting existing virtualbox VM for &quot;vault-cluster-m04&quot; ...
🌐  Found network options:
    ▪ NO_PROXY=192.168.99.120
    ▪ no_proxy=192.168.99.120
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
    ▪ env NO_PROXY=192.168.99.120
🔎  Verifying Kubernetes components...
👍  Starting node vault-cluster-m04 in cluster vault-cluster
🏃  Updating the running virtualbox &quot;vault-cluster-m04&quot; VM ...
🌐  Found network options:
    ▪ NO_PROXY=192.168.99.120,192.168.99.123
    ▪ no_proxy=192.168.99.120,192.168.99.123
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
    ▪ env NO_PROXY=192.168.99.120
    ▪ env NO_PROXY=192.168.99.120,192.168.99.123
🔎  Verifying Kubernetes components...
👍  Starting node vault-cluster-m04 in cluster vault-cluster
🏃  Updating the running virtualbox &quot;vault-cluster-m04&quot; VM ...
🌐  Found network options:
    ▪ NO_PROXY=192.168.99.120,192.168.99.123
    ▪ no_proxy=192.168.99.120,192.168.99.123
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.6 ...
    ▪ env NO_PROXY=192.168.99.120
    ▪ env NO_PROXY=192.168.99.120,192.168.99.123
🔎  Verifying Kubernetes components...
🏄  Done! kubectl is now configured to use &quot;vault-cluster&quot; cluster and &quot;default&quot; namespace by default
</code></pre>
<p>This is the output when I least the nodes:</p>
<pre><code>$ minikube node list -p vault-cluster
vault-cluster   192.168.99.120
vault-cluster-m04       192.168.99.123
vault-cluster-m04       192.168.99.123
vault-cluster-m04       192.168.99.123
</code></pre>
<p><a href="https://i.stack.imgur.com/Hcde6.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Hcde6.png" alt="enter image description here" /></a></p>
<p><strong>Any ideas what could be wrong?</strong></p>
<p>Environment:</p>
<ul>
<li><p>Windows 10 Pro</p>
</li>
<li><p>Virtual Box 6.1</p>
</li>
</ul>
<hr />
<pre><code>$ minikube version
minikube version: v1.20.0
commit: c61663e942ec43b20e8e70839dcca52e44cd85ae
</code></pre>
<hr />
<pre><code>$ kubectl version
Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;19&quot;, GitVersion:&quot;v1.19.7&quot;, GitCommit:&quot;1dd5338295409edcfff11505e7bb246f0d325d15&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2021-01-13T13:23:52Z&quot;, GoVersion:&quot;go1.15.5&quot;, Compiler:&quot;gc&quot;, Platform:&quot;windows/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;20&quot;, GitVersion:&quot;v1.20.2&quot;, GitCommit:&quot;faecb196815e248d3ecfb03c680a4507229c2a56&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2021-01-13T13:20:00Z&quot;, GoVersion:&quot;go1.15.5&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
</code></pre>

Eternal_N00B
<p>There seems to be some issue with minikube v1.20.0 and it also happens on linux with kvm2 driver (my setup) so it is not OS or driver specific.</p>
<p>It also happens on minikube v1.21.0, although it doesn't happen until stopped second time. After the first stop and start all seems to work fine but after second stop I see exactly what you see.</p>
<p>If you want you can create an <a href="https://github.com/kubernetes/minikube/issues" rel="nofollow noreferrer">issue on minikube githib repo</a> and hope developers fix it.</p>
