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

TestStartStop/group/crio: error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster #7808

Closed
medyagh opened this issue Apr 20, 2020 · 2 comments
Closed

TestStartStop/group/crio: error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster #7808

medyagh opened this issue Apr 20, 2020 · 2 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.10.0

Comments

@medyagh
Copy link
Member

medyagh commented Apr 20, 2020

as seen here
https://storage.googleapis.com/minikube-builds/logs/7785/573152f/Docker_Linux.html#fail_TestStartStop%2fgroup%2fcrio

[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/4.9.0-12-amd64\n", err: exit status 1
@medyagh medyagh added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Apr 20, 2020
@medyagh medyagh added this to the v1.10.0 milestone Apr 20, 2020
@medyagh medyagh mentioned this issue Apr 20, 2020
Merged
@tstromberg tstromberg changed the title TestStartStop/group/crio: ATAL: Module configs not found in directory /lib/modules/4.9.0-12-amd64\n", err: exit status 1 TestStartStop/group/crio: error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster Apr 21, 2020
@tstromberg
Copy link
Contributor

I believe that warning may be normal.

These are the more critical failures:

error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster

and

[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

Basically the kubelet is failing. Perhaps we should be invoking minikube logs to show the kubelet logs again when an integration test fails?

@medyagh medyagh added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 21, 2020
@priyawadhwa priyawadhwa mentioned this issue Apr 27, 2020
Merged
@sharifelgamal sharifelgamal mentioned this issue Apr 28, 2020
Merged
@medyagh
Copy link
Member Author

medyagh commented May 9, 2020

I have not seen this error in a while. I think this is closed.

@medyagh medyagh closed this as completed May 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. 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.10.0
Development

No branches or pull requests
2 participants
@tstromberg @medyagh