Delete the existing cluster if guest driver mismatch

[azhao155]

Delete the existing cluster if minikube start failed with GUEST_DRIVER_MISMATCH

zyanshu@zyanshukvm:~/minikube$ ./out/minikube start --driver=docker
😄  minikube v1.16.0 on Debian rodete
    ▪ MINIKUBE_ACTIVE_DOCKERD=p1
✨  Using the docker driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating docker container (CPUs=2, Memory=26100MB) ...
🐳  Preparing Kubernetes v1.20.0 on Docker 20.10.0 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔎  Verifying Kubernetes components...
🌟  Enabled addons: storage-provisioner, default-storageclass
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
zyanshu@zyanshukvm:~/minikube$ ./out/minikube start --driver=kvm2 --delete-on-failure
😄  minikube v1.16.0 on Debian rodete
    ▪ MINIKUBE_ACTIVE_DOCKERD=p1
❗  Start deleting cluster minikube with delete-on-failure flag set
🔥  Deleting "minikube" in docker ...
🔥  Deleting container "minikube" ...
🔥  Removing /usr/local/google/home/zyanshu/.minikube/machines/minikube ...
💀  Removed all traces of the "minikube" cluster.

💢  Exiting due to GUEST_DRIVER_MISMATCH: The existing "minikube" cluster was created using the "docker" driver, which is incompatible with requested "kvm2" driver. Deleted the existing 'minikube'
 cluster.
💡  Suggestion: Start the new 'minikube' cluster using: 'minikube start --driver=kvm2'

zyanshu@zyanshukvm:~/minikube$ ./out/minikube profile list

❌  Exiting due to MK_USAGE: No minikube profile was found. You can create one using `minikube start`.

[k8s-ci-robot]

Hi @azhao155. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: azhao155
To complete the pull request process, please assign priyawadhwa after the PR has been reviewed.
You can assign the PR to them by writing /assign @priyawadhwa in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[azhao155]

fix issue: #9399

[azhao155]

@medyagh

[minikube-bot]

Can one of the admins verify this patch?

[medyagh]

/ok-to-test

[medyagh]

/ok-to-test

[minikube-pr-bot]

kvm2 Driver
error collecting results for kvm2 driver: timing run 0 with Minikube (PR 10084): timing cmd: [/home/performance-monitor/.minikube/minikube-binaries/10084/minikube start --driver=kvm2]: starting cmd: fork/exec /home/performance-monitor/.minikube/minikube-binaries/10084/minikube: exec format error
docker Driver
error collecting results for docker driver: timing run 0 with Minikube (PR 10084): timing cmd: [/home/performance-monitor/.minikube/minikube-binaries/10084/minikube start --driver=docker]: starting cmd: fork/exec /home/performance-monitor/.minikube/minikube-binaries/10084/minikube: exec format error