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] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars {E2eNode Suite} #27668

Closed
k8s-github-robot opened this issue Jun 18, 2016 · 10 comments
Closed

[k8s.io] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars {E2eNode Suite} #27668

k8s-github-robot opened this issue Jun 18, 2016 · 10 comments
Assignees
@dchen1107
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@k8s-github-robot
Copy link

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

Failed: [k8s.io] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/downward_api_test.go:130
Expected error:
    <*errors.errorString | 0xc820a42e10>: {
        s: "gave up waiting for pod 'downward-api-05957d42-357e-11e6-a2fb-42010af00020' to be 'success or failure' after 5m0s",
    }
    gave up waiting for pod 'downward-api-05957d42-357e-11e6-a2fb-42010af00020' to be 'success or failure' after 5m0s
not to have occurred
@k8s-github-robot k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/flake Categorizes issue or PR as related to a flaky test. labels Jun 18, 2016
@nikhiljindal nikhiljindal mentioned this issue Jun 21, 2016
Merged
@nikhiljindal
Copy link
Contributor

Happened again: logs

@k8s-github-robot k8s-github-robot mentioned this issue Jun 21, 2016
Closed
@goltermann goltermann mentioned this issue Jun 23, 2016
Merged
@k8s-github-robot
Copy link
Author

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

Failed: [k8s.io] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/downward_api_test.go:130
Expected error:
    <*errors.errorString | 0xc820f9a5a0>: {
        s: "gave up waiting for pod 'downward-api-9147212c-3a49-11e6-a0a5-42010af0001e' to be 'success or failure' after 5m0s",
    }
    gave up waiting for pod 'downward-api-9147212c-3a49-11e6-a0a5-42010af0001e' to be 'success or failure' after 5m0s
not to have occurred

@ixdy ixdy mentioned this issue Jun 26, 2016
Merged
@fejta fejta mentioned this issue Jun 27, 2016
Merged
@xiangpengzhao xiangpengzhao mentioned this issue Jun 30, 2016
Merged
@k8s-github-robot k8s-github-robot mentioned this issue Aug 23, 2016
Closed
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/30730/node-pull-build-e2e-test/21335/

Failed: [k8s.io] Downward API should provide container's limits.cpu/memory and requests.cpu/memory as env vars {E2eNode Suite}

/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/downward_api.go:129
Expected error:
    <*errors.errorString | 0xc820684a70>: {
        s: "gave up waiting for pod 'downward-api-2141f0ee-6aec-11e6-9503-42010a80000a' to be 'success or failure' after 5m0s",
    }
    gave up waiting for pod 'downward-api-2141f0ee-6aec-11e6-9503-42010a80000a' to be 'success or failure' after 5m0s
not to have occurred
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2082

Happened on a presubmit run in #30730.

@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...

@yujuhong yujuhong mentioned this issue Aug 30, 2016
Closed
@yujuhong
Copy link
Contributor

Kubelet failed to admit the pod in question:

I0817 18:21:02.608269    3091 kubelet.go:2096] Predicate failed on Pod: downward-api-57fcb910-64a7-11e6-aaf4-42010a80001c_e2e-tests-downward-api-25dee(57fdfebe-64a7-11e6-b904-42010a80001c), for reason: Node didn't have enough resource: cpu, requested: 250, used: 1000, capacity: 1000

We should check whether we need to set a smaller cpu request for the tests as our nodes are smaller than what's in the regular e2e cluster.

@yujuhong yujuhong added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Aug 30, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @dchen1107

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

@k8s-github-robot k8s-github-robot mentioned this issue Sep 12, 2016
Closed
@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.

@yujuhong
Copy link
Contributor

Last failure was >2 months ago. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dchen1107 dchen1107

Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dchen1107 @nikhiljindal @yujuhong @k8s-github-robot