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

[k8s.io] Load capacity [Feature:Performance] should be able to handle 30 pods per node {Kubernetes e2e suite} #33711

Closed
k8s-github-robot opened this issue Sep 29, 2016 · 3 comments
Closed

[k8s.io] Load capacity [Feature:Performance] should be able to handle 30 pods per node {Kubernetes e2e suite} #33711

k8s-github-robot opened this issue Sep 29, 2016 · 3 comments
Assignees
@wojtek-t
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.

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-kubemark-500-gce/6275/

Failed: [k8s.io] Load capacity [Feature:Performance] should be able to handle 30 pods per node {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/load.go:206
scaling rc load-medium-rc-72 for the first time
Expected error:
    <*errors.errorString | 0xc82d911380>: {
        s: "error while scaling RC load-medium-rc-72 to 23 replicas: Scaling the resource failed with: Get https://104.197.104.157/api/v1/namespaces/e2e-tests-load-30-nodepods-3-7ya8x/replicationcontrollers/load-medium-rc-72: http2: no cached connection was available; Current resource version Unknown",
    }
    error while scaling RC load-medium-rc-72 to 23 replicas: Scaling the resource failed with: Get https://104.197.104.157/api/v1/namespaces/e2e-tests-load-30-nodepods-3-7ya8x/replicationcontrollers/load-medium-rc-72: http2: no cached connection was available; Current resource version Unknown
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/load.go:327

Previous issues for this test: #26544 #26938 #27595 #30146 #30469 #31374 #31427 #31433 #31589 #31981 #32257
@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 29, 2016
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-kubemark-500-gce/6284/

Failed: [k8s.io] Load capacity [Feature:Performance] should be able to handle 30 pods per node {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/load.go:206
scaling rc load-small-rc-1024 for the first time
Expected error:
    <*errors.errorString | 0xc8236a8f50>: {
        s: "error while scaling RC load-small-rc-1024 to 5 replicas: Scaling the resource failed with: Get https://104.198.171.27/api/v1/namespaces/e2e-tests-load-30-nodepods-5-3v7bf/replicationcontrollers/load-small-rc-1024: http2: no cached connection was available; Current resource version Unknown",
    }
    error while scaling RC load-small-rc-1024 to 5 replicas: Scaling the resource failed with: Get https://104.198.171.27/api/v1/namespaces/e2e-tests-load-30-nodepods-5-3v7bf/replicationcontrollers/load-small-rc-1024: http2: no cached connection was available; Current resource version Unknown
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/load.go:327

@wojtek-t wojtek-t mentioned this issue Sep 29, 2016
Merged
@wojtek-t
Copy link
Member

We understand the problem here - I'm working on the fix.

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-kubemark-500-gce/6295/

Failed: [k8s.io] Load capacity [Feature:Performance] should be able to handle 30 pods per node {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/load.go:206
scaling rc load-small-rc-1242 for the first time
Expected error:
    <*errors.errorString | 0xc8244b3410>: {
        s: "error while scaling RC load-small-rc-1242 to 6 replicas: Scaling the resource failed with: Get https://104.198.166.253/api/v1/namespaces/e2e-tests-load-30-nodepods-3-jjujp/replicationcontrollers/load-small-rc-1242: http2: no cached connection was available; Current resource version Unknown",
    }
    error while scaling RC load-small-rc-1242 to 6 replicas: Scaling the resource failed with: Get https://104.198.166.253/api/v1/namespaces/e2e-tests-load-30-nodepods-3-jjujp/replicationcontrollers/load-small-rc-1242: http2: no cached connection was available; Current resource version Unknown
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/load.go:327

@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 Sep 29, 2016
k8s-github-robot pushed a commit that referenced this issue Sep 29, 2016
Merge pull request #33733 from wojtek-t/fix_http2
8dd83dd 
Automatic merge from submit-queue

Use multiple clients in load test to avoid "no cached connections" er…

Fix #33711
@k8s-github-robot k8s-github-robot mentioned this issue Sep 30, 2016
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Nov 10, 2016
Closed
This was referenced Nov 18, 2016
Closed
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Apr 24, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wojtek-t wojtek-t

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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wojtek-t @k8s-github-robot