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

[Flaky test] [sig-apps] DaemonRestart [Disruptive] Kubelet should not restart containers across restart #75373

Open
mariantalla opened this Issue Mar 14, 2019 · 3 comments

Comments

@mariantalla
Copy link
Contributor

mariantalla commented Mar 14, 2019

Which jobs are failing:

Which test(s) are failing:
[sig-apps] DaemonRestart [Disruptive] Kubelet should not restart containers across restart

Reason for failure:
A timeout while deleting the namespace:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:152
Mar 13 23:56:13.750: Couldn't delete ns: "daemonrestart-7581": namespace daemonrestart-7581 was not deleted with limit: timed out waiting for the condition, pods remaining: 1 (&errors.errorString{s:"namespace daemonrestart-7581 was not deleted with limit: timed out waiting for the condition, pods remaining: 1"})
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:342

Anything else we need to know

  • This test flakes about 10% of the time at the moment.

/sig apps
/remove-kind failing-test
/kind flake
/priority important-soon
/milestone v1.14

cc @smourapina @alejandrox1 @kacole2 @mortent

@mariantalla

This comment has been minimized.

Copy link
Contributor Author

mariantalla commented Mar 15, 2019

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Mar 16, 2019

Looking back a week ago, it seems like at least one major cluster started happening around March 1st, so possibly related to go 1.12
https://storage.googleapis.com/k8s-gubernator/triage/index.html?date=2019-03-09&test=DaemonRestart#24a9e90c86eb2ad855a0

This may be worth keeping an eye on now that go 1.12.1 has been introduced #74890

@spiffxp spiffxp moved this from Flakes to Open PR-wait for >5 successes before "Resolved" in 1.14 CI Signal Mar 16, 2019

@mariantalla

This comment has been minimized.

Copy link
Contributor Author

mariantalla commented Mar 18, 2019

No failures since March 15th in master-blocking:
image

or 1.14-blocking
image

Let's keep an eye on it for a couple more days.

@mariantalla mariantalla moved this from Open PR-wait for >5 successes before "Resolved" to Resolved flakes (observe closed for a week before "Resolved") in 1.14 CI Signal Mar 18, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.