profile list for multi node shows error wrongfully

[medyagh]

as noted by @sharifelgamal the missing part of this PR is left #9702 (comment)

|----------|-----------|---------|--------------|------|---------|---------|-------|
| Profile  | VM Driver | Runtime |      IP      | Port | Version | Status  | Nodes |
|----------|-----------|---------|--------------|------|---------|---------|-------|
| minikube | docker    | docker  | 192.168.49.2 | 8443 | v1.19.4 | Running |     1 |
| p2       | docker    | docker  | 192.168.59.2 | 8443 | v1.19.4 | Running |     2 |
|----------|-----------|---------|--------------|------|---------|---------|-------|
❗  Found 1 invalid profile(s) ! 
	 p2-m02
💡  You can delete them using the following command(s): 
	 $ minikube delete -p p2-m02 

[daehyeok]

Do we have any reason check both of directory and container in the ListProfiles func?

minikube/pkg/minikube/config/profile.go

Line 197 in b4bf2bd

func ListProfiles(miniHome ...string) (validPs []*Profile, inValidPs []*Profile, err error) {

Is it added to remove all nodes when run delete profile command(58b637b)? It looks nodes and profiles are not distinguished in the function. (E.g. seconds node p2-m02 also returned as invalid 'profile' by ListProfiles func).

Currently, returned invalidProfiles used only for List, Delete, Valid profile. I'm not sure if i remove sub node(profile) from ListProfiles's result(but also change Delete profile function to keep handling multiple nodes), It will have potential problems or not.

[medyagh]

one reason I am thinking is in the clean up process, when there is no minikube config,
we use the existing Directory as Possible left over minikubes so we use that delete minikube left over containers

[medyagh]

so imagine u create minikube with docker
then u delete minikube home (config) now the containers are still there ... but we wanna clean up the minikube if someone says "minikube delete --all"
https://github.com/medyagh/minikube/blob/0a5ef42ed548d65694b6d96b487fbe0bf8b3db01/pkg/minikube/machine/delete.go#L39

[daehyeok]

Is it anyway to check node is part of multnode cluster or not?