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

[k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite} #33547

Closed
k8s-github-robot opened this issue Sep 27, 2016 · 45 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/node Categorizes an issue or PR as relevant to SIG Node.
Milestone

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-serial-gce-e2e-ci/839/

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Sep 27 09:51:41.167: CPU usage exceeding limits:
 node tmp-node-e2e-14ffd611-coreos-alpha-1122-0-0-v20160727:
 container "kubelet": expected 95th% usage < 0.500; got 0.514
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:278

Previous issues for this test: #30523 #32022 #33291

@k8s-github-robot k8s-github-robot added kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Sep 27, 2016
@k8s-github-robot
Copy link
Author

k8s-github-robot commented Sep 30, 2016

Builds:
kubelet-serial-gce-e2e-ci 875 901 964 1074 1112

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Expected error:
    <*errors.errorString | 0xc821284b80>: {
        s: "too high pod startup latency 50th percentile: 16.11351258s",
    }
    too high pod startup latency 50th percentile: 16.11351258s
not to have occurred
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:554

@k8s-github-robot
Copy link
Author

k8s-github-robot commented Oct 2, 2016

Builds:
kubelet-serial-gce-e2e-ci 899 966 1012 1018 1037 1086 1121 1182 1214 1226 1230 1237 1298 1302 1309 1328 1366 1404 1405 1413 1417 1420

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Oct  2 02:31:22.805: CPU usage exceeding limits:
 node tmp-node-e2e-d61a0e68-coreos-alpha-1122-0-0-v20160727:
 container "kubelet": expected 95th% usage < 0.500; got 0.561
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:278

@k8s-github-robot k8s-github-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Oct 2, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot k8s-github-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 2, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

11 similar comments
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-serial-gce-e2e-ci/1206/

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Oct 26 16:50:01.595: CPU usage exceeding limits:
 node tmp-node-e2e-3085feef-e2e-node-containervm-v20160604-image:
 container "runtime": expected 95th% usage < 0.600; got 0.654
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:281

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

2 similar comments
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-serial-gce-e2e-ci/1297/

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Nov  2 21:17:25.749: CPU usage exceeding limits:
 node tmp-node-e2e-e6d67020-coreos-alpha-1122-0-0-v20160727:
 container "kubelet": expected 50th% usage < 0.300; got 0.301, container "kubelet": expected 95th% usage < 0.500; got 0.601
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:281

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

2 similar comments
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @zmerlynn

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

This flaky-test issue would love to have more attention.

@saad-ali
Copy link
Member

@dchen1107 Can you please help triage this issue for 1.5

CC @calebamiles

@k8s-github-robot
Copy link
Author

k8s-github-robot commented Nov 14, 2016

Builds:
kubelet-serial-gce-e2e-ci 1447 1452 1455 1465 1471

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Nov 14 22:19:40.118: CPU usage exceeding limits:
 node tmp-node-e2e-ba2f4c87-coreos-alpha-1122-0-0-v20160727:
 container "kubelet": expected 95th% usage < 0.500; got 0.532
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:281

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

This flaky-test issue would love to have more attention.

@calebamiles
Copy link
Contributor

This seems like a somewhat flaky test, could @dchen1107, @yujuhong, or someone from @kubernetes/sig-node please advise as to whether this issue should block the release. Thanks!

cc: @saad-ali, @dims

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-serial-gce-e2e-ci/1477/

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Nov 17 10:46:44.503: CPU usage exceeding limits:
 node tmp-node-e2e-0b6d402c-coreos-alpha-1122-0-0-v20160727:
 container "kubelet": expected 95th% usage < 0.500; got 0.515
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:281

@calebamiles
Copy link
Contributor

@dchen1107, @kubernetes/sig-node all issues must be labeled either release blocker or non release blocking by end of day 18 November 2016 PST. If you are not the correct owner please identify the correct owner and add them to this thread for assignment.

cc: @saad-ali, @dims

@dchen1107
Copy link
Member

We plan to remove those tests to node soaking tests, not serial test suite.

@yujuhong
Copy link
Contributor

@dchen1107, this is not the regular resource usage test that measures during the steady state. This is the density test written by @coufon. This test measures resource usage during pod creation for tracking regression. They won't add much value to the soak suite.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

This flaky-test issue would love to have more attention.

2 similar comments
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-serial/8/

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Nov 24 17:49:52.141: CPU usage exceeding limits:
 node tmp-node-e2e-b8e548ec-coreos-alpha-1122-0-0-v20160727:
 container "kubelet": expected 95th% usage < 0.500; got 0.564
/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:281

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

This flaky-test issue would love to have more attention.

1 similar comment
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

This flaky-test issue would love to have more attention.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-serial/20/

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:67
Expected error:
    <*errors.errorString | 0xc82029cf50>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:67

@dims
Copy link
Member

dims commented Dec 9, 2016

@dchen1107 Is it appropriate to move this to the next milestone or clear the 1.5 milestone? (and remove the non-release-blocker tag as well)

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet-serial/24/

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:67
Expected error:
    <*errors.errorString | 0xc82029d130>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:68

@k8s-github-robot
Copy link
Author

k8s-github-robot commented Dec 17, 2016

Builds:
ci-kubernetes-node-kubelet-serial 31 33

Failed: [k8s.io] Density [Serial] [Slow] create a batch of pods latency/resource should be within limit when create 10 pods with 0 interval {E2eNode Suite}

/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/density_test.go:109
Dec 17 18:04:43.483: CPU usage exceeding limits:
 node tmp-node-e2e-4eef70e5-coreos-alpha-1122-0-0-v20160727:
 container "kubelet": expected 95th% usage < 0.500; got 0.526
/var/lib/jenkins/workspace/ci-kubernetes-node-kubelet-serial/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:281

@calebamiles calebamiles modified the milestones: v1.5, v1.6 Mar 4, 2017
@derekwaynecarr
Copy link
Member

no occurrence in 2017, closing per 1.6 guidance.

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/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

8 participants