-
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
Show info about the minikube linux distribution #4525
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund 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 |
/retest this please |
there is a lint issue
|
/lint |
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.
@RA489: 0 warnings.
In response to this:
/lint
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@minikube-bot OK to test |
I like this PR. I do agree that showing the distro is of most importance for the none drivers, but I would also like to show it for other platforms. We have the perfect space for it here:
What I propose is to place it here:
In the future I would also like to extend this to Mac OS X & Windows as well, but surprisingly, I can't find any good libraries for doing so. That said, I'm perfectly OK with this approach as a stop-gap measure. |
@minikube-bot OK to test This can be merged once lint issues are addressed. |
They are talking about different things. One is showing information about the The other is showing information from the libmachine provisioner, i.e. what is being installed on the VM. Currently I used the same information also for the |
Most other operating systems have this in their |
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.
Looks good to me
/retest this please |
1 similar comment
/retest this please |
@minikube-bot OK to test |
Curious failure:
Also, the Travis timeout makes me wonder if a unit test is starting up a real minikube rather than using mocks. |
@minikube-bot OK to test |
Looks like this one has a merge conflict now :( |
Ok, rebase time perhaps |
793b8a4
to
44e50d4
Compare
Moved into a proper function |
go tests are still timing out in travis, so I wonder if additional mocking may be required?
|
Yes, there is something wrong with DetectProvisioner. Think we have seen this elsewhere too ?
|
Maybe should scope out the provisioned linux distribution for now. There's only one, anyway...
|
Here is where it was seen before: #4132
|
It seems that these tests have always been timing out, since they use VirtualBox and not Mock host... Before: (6 minutes wasted!) After: (half a second now...) That is, we seem to be calling SSH a lot for drivers ( |
/retest was checking translations, and some weird sshutil error ? |
I think we've now addressed cluster_test, sshutil, and translation check issues. Sorry about the instability there! |
Taking from /etc/os-release, via libmachine provision Failure to show it is not fatal, just log an error...
Seems there is a bug in the MockDriver, where it returns |
Makes it more clear that it is os-release(5)
Not very friendly to return nil without error
Taking from /etc/os-release, via libmachine provision
For #4523