Skip to content
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.

Sign up for GitHub

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

Jump to bottom

logs no longer include libmachine commands, making hyperv impossible to debug #5453

Closed
tstromberg opened this issue Sep 24, 2019 · 4 comments · Fixed by #5574
Closed

logs no longer include libmachine commands, making hyperv impossible to debug #5453

tstromberg opened this issue Sep 24, 2019 · 4 comments · Fixed by #5574
Assignees
@sharifelgamal
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.5.0

Comments

@tstromberg
Copy link
Contributor

We used to have logs for Hyper-V and Virtualbox machine drivers that showed each command run. Where'd they go?
@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 24, 2019
This was referenced Sep 24, 2019
Closed
Closed
@tstromberg tstromberg changed the title VM logs aren't what they used to be logs no longer include libmachine commands, making hyperv impossible to debug Oct 2, 2019
@tstromberg tstromberg added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Oct 2, 2019
@tstromberg tstromberg added this to the v1.5.0 milestone Oct 2, 2019
@tstromberg tstromberg mentioned this issue Oct 2, 2019
Closed
@tstromberg
Copy link
Contributor Author

git bisect to the rescue!

@sharifelgamal
Copy link
Collaborator

git bisect points to #5241 as the culprit, which I'm not 100% sure I understand, I'm digging in some more.

@tstromberg
Copy link
Contributor Author

tstromberg commented Oct 8, 2019 •
edited
Loading

Any update?

@sharifelgamal
Copy link
Collaborator

not really, it's definitely in libmachine, but that really hasn't changed so maybe it's how we call it?

@sharifelgamal sharifelgamal mentioned this issue Oct 9, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sharifelgamal sharifelgamal

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.5.0
Development

Successfully merging a pull request may close this issue.

Add libmachine debug logs back sharifelgamal/minikube
2 participants
@tstromberg @sharifelgamal