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

TestFunctional/parallel/ComponentHealth flake on docker #8014

Closed
priyawadhwa opened this issue May 5, 2020 · 4 comments · Fixed by #8199
Closed

TestFunctional/parallel/ComponentHealth flake on docker #8014

priyawadhwa opened this issue May 5, 2020 · 4 comments · Fixed by #8199
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@priyawadhwa
Copy link

Original logs here

functional_test.go:288: (dbg) Run:  kubectl --context functional-20200505192422-29695 get cs -o=json
functional_test.go:307: unexpected status: False - item: {TypeMeta:{Kind:ComponentStatus APIVersion:v1} ObjectMeta:{Name:controller-manager GenerateName: Namespace: SelfLink:/api/v1/componentstatuses/controller-manager UID: ResourceVersion: Generation:0 CreationTimestamp:0001-01-01 00:00:00 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[]} Conditions:[{Type:Healthy Status:False Message:Get http://127.0.0.1:10252/healthz: dial tcp 127.0.0.1:10252: connect: connection refused Error:}]}
@priyawadhwa priyawadhwa added 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. labels May 5, 2020
@medyagh medyagh added this to the v1.11.0 milestone May 9, 2020
@medyagh medyagh added the kind/flake Categorizes issue or PR as related to a flaky test. label May 11, 2020
@medyagh
Copy link
Member

medyagh commented May 11, 2020

I still see this on HEAD today

@medyagh
Copy link
Member

medyagh commented May 11, 2020

@priyawadhwa
Copy link
Author

According to Thomas's passrate script, this test has been a little flaky but passed on docker today:

$ /home/tstromberg/bin/passrate.sh TestFunctional/parallel/ComponentHealth
-------------------------------------------------
docker_Linux      | 2020-05-14 |  67% | 8 of 12
docker_Linux      | 2020-05-15 |  75% | 9 of 12
docker_Linux      | 2020-05-16 |  75% | 9 of 12
docker_Linux      | 2020-05-17 |  92% | 11 of 12
docker_Linux      | 2020-05-18 | 100% | 8 of 8

it also seemed to fail once today on KVM

KVM_Linux         | 2020-05-14 | 100% | 10 of 10
KVM_Linux         | 2020-05-15 |  92% | 11 of 12
KVM_Linux         | 2020-05-16 |  92% | 12 of 13
KVM_Linux         | 2020-05-17 | 100% | 11 of 11
KVM_Linux         | 2020-05-18 |  88% | 7 of 8

I'll do some digging.

To run locally:

make integration -e TEST_ARGS="-test.run TestFunctional/parallel/ComponentHealth --profile=minikube --cleanup=false --minikube-start-args="--driver=docker""

@priyawadhwa priyawadhwa removed the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label May 18, 2020
@priyawadhwa
Copy link
Author

Most recent logs from #8168 can be found here

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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants