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

docker: TestStartStop/group/crio: Found multiple CRI sockets, please use --cri-socket #7721

Closed
medyagh opened this issue Apr 16, 2020 · 4 comments · Fixed by #7724 or #7780
Closed
Assignees
Labels
co/docker-driver Issues related to kubernetes in container co/kubeadm Issues relating to kubeadm co/runtime/crio CRIO related issues 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

Comments

@medyagh
Copy link
Member

medyagh commented Apr 16, 2020

	W0416 08:08:07.917337    9367 kubeadm.go:299] delete failed: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.15.7:$PATH kubeadm reset --force": Process exited with status 1
	stdout:
	[reset] Reading configuration from the cluster...
	[reset] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
	stderr:
	W0416 15:08:07.879498   27209 reset.go:98] [reset] Unable to fetch the kubeadm-config ConfigMap from cluster: failed to get config map: Get https://172.17.0.3:8443/api/v1/namespaces/kube-system/configmaps/kubeadm-config: dial tcp 172.17.0.3:8443: connect: connection refused
	Found multiple CRI sockets, please use --cri-socket to select one: /var/run/dockershim.sock, /var/run/crio/crio.sock

https://storage.googleapis.com/minikube-builds/logs/7705/c44655c/Docker_Linux.html#fail_TestStartStop%2fgroup%2fcrio

@medyagh medyagh added this to the v1.10.0 milestone Apr 16, 2020
@medyagh
Copy link
Member Author

medyagh commented Apr 16, 2020

@afbjorklund showed interest in this one but if anyone else likes to take a look plz let me know,

@afbjorklund afbjorklund added co/docker-driver Issues related to kubernetes in container co/kubeadm Issues relating to kubeadm kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. labels Apr 16, 2020
@tstromberg tstromberg changed the title Failing Test: TestStartStop/group/crio on docker driver docker: TestStartStop/group/crio: Found multiple CRI sockets, please use --cri-socket Apr 16, 2020
@medyagh medyagh added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. co/runtime/crio CRIO related issues labels Apr 16, 2020
@tstromberg
Copy link
Contributor

tstromberg commented Apr 17, 2020

Based on uptick in frequency, this seems highly correlated to #7580

Frequency per day
-----------------
      2 2020-04-01
      1 2020-04-07
     14 2020-04-10
     14 2020-04-11
     16 2020-04-12
     20 2020-04-13
     20 2020-04-14
     22 2020-04-15
     26 2020-04-16

Oldest 5 matches
---------------------

==> /var/lib/jenkins/jobs/docker_Linux_integration/builds/1545/Docker_Linux.txt <==
 GitHub pull request #7580 of commit 204e469eeb3340cec118daec7b6cd6ab255b0ae2, no merge conflicts.
>> Starting at Fri Apr 10 03:17:17 PDT 2020
minikube version: v1.9.2
commit: 4588c86df310e62a2d2ca4ef268c146f48ef6d76

==> /var/lib/jenkins/jobs/docker_Linux_integration/builds/1542/Docker_Linux.txt <==
 GitHub pull request #7580 of commit 4dd2152fae8123ca9573bf716839ab8d93f16d5d, no merge conflicts.
>> Starting at Fri Apr 10 01:53:12 PDT 2020
minikube version: v1.9.2
commit: 665d5739d73e5eb0d8f9ef9f4d7675ca1c2ca62d

==> /var/lib/jenkins/jobs/docker_Linux_integration/builds/1442/Docker_Linux.txt <==
 GitHub pull request #7484 of commit e120758639eb427a73aa20d69b1fe9b04fe2a724, no merge conflicts.
>> Starting at Tue Apr  7 11:03:34 PDT 2020
minikube version: v1.9.2
commit: 157d7a4e3cde2d8f9765dcf9d2332aeb6863222d

==> /var/lib/jenkins/jobs/docker_Linux_integration/builds/1318/Docker_Linux.txt <==
 GitHub pull request #7364 of commit 071b2c11a44139d9d506a4e558aed36fe5b672d5, no merge conflicts.
>> Starting at Wed Apr  1 18:30:52 PDT 2020
minikube version: v1.9.0
commit: 3f9f72fb5380c02b30317fc8a7578249f806c002

==> /var/lib/jenkins/jobs/docker_Linux_integration/builds/1314/Docker_Linux.txt <==
 GitHub pull request #7364 of commit 72cc9cb7c1b107181bbef243b21e77e1ae769bd0, no merge conflicts.
>> Starting at Wed Apr  1 16:53:02 PDT 2020
minikube version: v1.9.0
commit: 58407cc5cbf80971c3794e35cca782922bce9df1

@tstromberg
Copy link
Contributor

The passrate for this test is 0%:

docker_Linux      | 2020-04-13 |   0% | 0 of 10
docker_Linux      | 2020-04-14 |   0% | 0 of 11
docker_Linux      | 2020-04-15 |   0% | 0 of 11
docker_Linux      | 2020-04-16 |   0% | 0 of 12
docker_Linux      | 2020-04-17 |   0% | 0 of 4

If this becomes a release blocker, I recommend reverting #7580

@afbjorklund
Copy link
Collaborator

Was reverted by medyagh in #7751 but apparently still works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/docker-driver Issues related to kubernetes in container co/kubeadm Issues relating to kubeadm co/runtime/crio CRIO related issues 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
3 participants