Provide more descriptive error codes for GUEST_PROVISIONG

[nelango]

GUEST_PROVISION comprises 8.5% of minikube start errors in our environment.

These could be because minikube failed to obtain driver options/ generate cluster config/ cache minikube ISO.

Can minikube provide more descriptive error codes for their scenarios? It would also help to make the error messages actionable wherever possible.

[tstromberg]

As a catchall error code, In order to break this code down further, we'll need to collect example error messages for known issues. We can then add support for them here:

https://github.com/kubernetes/minikube/blob/master/pkg/minikube/reason/known_issues.go

[tstromberg]

Here's the best advice I have for collecting this info:

https://github.com/kubernetes/minikube/issues?q=is%3Aissue+GUEST_PROVISION

Looks like we have 21 examples currently that can get broken down to more specific exit codes.

[tstromberg]

I noticed at least one bug here in #10151 - it should have raised PR_DOCKER_NO_SSH instead of GUEST_PROVISION. This makes me wonder if there is a bug that is causing known_issues to not be parsed.

UPDATE: I misread the text, the two errors are very similar, but not identical.

[azhao155]

/assign @azhao155

[medyagh]

@azhao155 has too many tasks this milestone, I unassign it for now if anyone wants to pick it up

[spowelljr]

In-progress