unable to delete node "minikube-m02": nodes "minikube-m02" not found

[xinmans]

What Happened?

root@unraid:/homelab# minikube node list
minikube 192.168.50.17
minikube-m02
minikube-m03 192.168.50.144
root@unraid:/homelab# minikube node delete minikube-m02
🔥 Deleting node minikube-m02 from cluster minikube
E1207 17:08:08.381296 7973 node.go:122] unable to delete node "minikube-m02": nodes "minikube-m02" not found

❌ Exiting due to GUEST_NODE_DELETE: nodes "minikube-m02" not found

Attach the log file

minikube-m02 no ip

Operating System

Other

Driver

KVM2

[xinmans]

OS:
Linux unraid 5.10.28-Unraid #1 SMP Thu Apr 15 02:04:16 CST 2021 x86_64 Intel(R) Core(TM) i3-8100B CPU @ 3.60GHz GenuineIntel GNU/Linux

[kundan2707]

/kind support

[spowelljr]

Hi @xinmans, either minikube-m02 wasn't started correctly on initial start, or it later got deleted outside of minikube.

Could you try deleting the entire cluster via minikube delete and then try starting it again and see if minikube node list returns an IP for minikube-m02 immediately after startup. If it was working for a while and recently stopped it would seem the container got deleted by outside of minikube.

[xinmans]

I can't minikube delete,coz I have install a few services, any other solution?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.