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.

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

Linux VirtualBox TestStartStop: failure loading etcd/ca certificate authority: the certificate is not valid yet #3433

Closed
balopat opened this issue Dec 8, 2018 · 2 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@balopat
Copy link
Contributor

balopat commented Dec 8, 2018

This seems similar to #3196:

    		[init] Using Authorization modes: [Node RBAC]
    		[preflight] Running pre-flight checks.
    			[WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 18.06.1-ce. Max validated version: 17.03
    			[WARNING Swap]: running with swap on is not supported. Please disable swap
    		Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version.
    		[certificates] Using the existing ca certificate and key.
    		[certificates] Using the existing apiserver certificate and key.
    		[certificates] Generated apiserver-kubelet-client certificate and key.
    		[certificates] Generated etcd/ca certificate and key.
    		[certificates] Generated etcd/server certificate and key.
    		failure loading etcd/ca certificate authority: the certificate is not valid yet
    		[certificates] etcd/server serving cert is signed for DNS names [localhost] and IPs [127.0.0.1]

Example: https://storage.googleapis.com/minikube-builds/logs/3432/Linux-VirtualBox.txt

@balopat balopat added the kind/flake Categorizes issue or PR as related to a flaky test. label Dec 8, 2018
@balopat balopat changed the title Linux VirtualBox: Linux VirtualBox TestStartStop: failure loading etcd/ca certificate authority: the certificate is not valid yet Dec 8, 2018
@balopat balopat mentioned this issue Dec 8, 2018
@tstromberg
Copy link
Contributor

FYI, I think this might be because when guest VM is synced against a different time source than the host VM.

When possible for sanity sake, the guest should sync against the host. I think I noticed code that syncs against time?.google.com

@tstromberg
Copy link
Contributor

Dupe of #2749

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Development

No branches or pull requests

2 participants