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

E2E Test failure: [k8s.io] Loadbalancing: L7 [k8s.io] [Slow] Nginx should conform to Ingress spec (Failure cluster [1e796c...] failed 121 builds, 23 jobs, and 3 tests over 1 days) #47397

Closed
k8s-github-robot opened this issue Jun 13, 2017 · 4 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/network Categorizes an issue or PR as relevant to SIG Network.
Milestone

Comments

@k8s-github-robot
Copy link

Failure cluster 1e796c09ea87722d28c5

Error text:
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/ingress.go:194
Jun 12 11:41:19.409: Ingress failed to acquire an IP address within 15m0s
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/ingress_utils.go:900
Failure cluster statistics:

3 tests failed, 23 jobs failed, 121 builds failed.
Failure stats cover 1 day time range '12 Jun 2017 04:03 UTC' to '13 Jun 2017 04:03 UTC'.

Top failed tests by jobs failed:
Test Name Jobs Failed
[k8s.io] Loadbalancing: L7 [k8s.io] Nginx should conform to Ingress spec 14
[k8s.io] Loadbalancing: L7 [k8s.io] [Slow] Nginx should conform to Ingress spec 8
[k8s.io] Loadbalancing: L7 [k8s.io] GCE [Slow] [Feature:Ingress] should conform to Ingress spec 1
Top failed jobs by builds failed:
Job Name Builds Failed Latest Failure
ci-kubernetes-e2e-gci-gke-multizone 9 12 Jun 2017 23:18 UTC
ci-kubernetes-e2e-gci-gce-proto 9 12 Jun 2017 23:19 UTC
ci-kubernetes-e2e-gci-gce 9 12 Jun 2017 23:09 UTC
Rationale for assignments:
Assignee or SIG area Owns test(s)
ncdc [k8s.io] Loadbalancing: L7 [k8s.io] Nginx should conform to Ingress spec; [k8s.io] Loadbalancing: L7 [k8s.io] [Slow] Nginx should conform to Ingress spec
derekwaynecarr [k8s.io] Loadbalancing: L7 [k8s.io] GCE [Slow] [Feature:Ingress] should conform to Ingress spec
sig/network [k8s.io] Loadbalancing: L7 [k8s.io] Nginx should conform to Ingress spec; [k8s.io] Loadbalancing: L7 [k8s.io] [Slow] Nginx should conform to Ingress spec; [k8s.io] Loadbalancing: L7 [k8s.io] GCE [Slow] [Feature:Ingress] should conform to Ingress spec

Current Status

@k8s-github-robot k8s-github-robot added kind/flake Categorizes issue or PR as related to a flaky test. sig/network Categorizes an issue or PR as relevant to SIG Network. labels Jun 13, 2017
@nicksardo
Copy link
Contributor

#47362 (comment)

@nicksardo
Copy link
Contributor

nicksardo commented Jun 13, 2017

Looks like fluentd exposes port 80 and causes the conflict. Tests started failing after #46539 was merged.
@dchen1107 @crassirostris

Thanks for your help @aledbf

@nicksardo
Copy link
Contributor

/assign @crassirostris

@crassirostris
Copy link

@nicksardo Thanks!

@dchen1107 dchen1107 changed the title Failure cluster [1e796c...] failed 121 builds, 23 jobs, and 3 tests over 1 days E2E Test failure: [k8s.io] Loadbalancing: L7 [k8s.io] [Slow] Nginx should conform to Ingress spec (Failure cluster [1e796c...] failed 121 builds, 23 jobs, and 3 tests over 1 days) Jun 13, 2017
@dchen1107 dchen1107 added this to the v1.7 milestone Jun 13, 2017
k8s-github-robot pushed a commit that referenced this issue Jun 14, 2017
Automatic merge from submit-queue (batch tested with PRs 47302, 47389, 47402, 47468, 47459)

Change port on which fluentd exposes its metrics

Fix #47397

/cc @Q-Lee @nicksardo

```release-note
Stackdriver Logging deployment exposes metrics on node port 31337 when enabled.
```
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. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

6 participants