Automatic restart is hiding the real error

[afbjorklund]

We get a lot of reports, that include a partial log from the restart - but nothing from the inital start.

It would be nice to improve this, to either fail on the first error or show how to report all logs ?

Typical report:

✨ Using the docker driver based on existing profile
🤷 docker "minikube" container is missing, will recreate.

• Using the virtualbox driver based on existing profile
• Restarting existing virtualbox VM for "minikube" ...

The details from the first start, that shows why it fails, is not included in the bug report or logs.

[medyagh]

I was thinking we should by default write your logs for the current start to ~/.minikube/logs.txt or something, so whenever user does not run with --aloslogtostderr we should be able to ask them just pass ~/.minikube/logs.txt

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[tstromberg]

I believe this has been addressed. If someone sees this again, please re-open with an example.