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 pod IP as an env var {E2eNode Suite} #30794

Closed
k8s-github-robot opened this issue Aug 17, 2016 · 3 comments
Closed

[k8s.io] Downward API should provide pod IP as an env var {E2eNode Suite} #30794

k8s-github-robot opened this issue Aug 17, 2016 · 3 comments
Labels
area/node-e2e 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/pr-logs/pull/30360/node-pull-build-e2e-test/19452/

Failed: [k8s.io] Downward API should provide pod IP as an env var {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:83
Expected error:
    <*errors.errorString | 0xc820172c80>: {
        s: "gave up waiting for pod 'downward-api-57fcb910-64a7-11e6-aaf4-42010a80001c' to be 'success or failure' after 5m0s",
    }
    gave up waiting for pod 'downward-api-57fcb910-64a7-11e6-aaf4-42010a80001c' 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:2072

Happened on a presubmit run in #30360.
@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 Aug 17, 2016
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @nhlfr

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

@yujuhong yujuhong added sig/node Categorizes an issue or PR as relevant to SIG Node. area/node-e2e labels Aug 30, 2016
@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
Copy link
Contributor

Dup of #27668

@k8s-github-robot k8s-github-robot mentioned this issue Sep 12, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/node-e2e 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
3 participants
@nhlfr @yujuhong @k8s-github-robot