-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make hyperkit driver more robust: detect crashing, misinstallation, other process names #3660
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tstromberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@minikube-bot OK to test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I HIGHLY approve of adding more log.Info messages around tricky start up moments like this
@minikube-bot OK to test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you
As discussed, one more suggestion for even better debuggability:
in driver.go, Start()
logger := log.New(os.Stdout, "hyperkit server - ", 0)
h.SetLogger(logger)
Things I ran into today when I had an older hyperkit driver installed and tried to update it, badly.
Also adds logging for DHCP lease discovery.