kubernetes: [Failing test] gce-cos--ingress are timing out
Which jobs are failing:
Which test(s) are failing: The jobs are timing out, but just before that, the following tests failed:
[sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should be able to switch between HTTPS and HTTP2 modes[sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should update ingress while sync failures occur on other ingresses[sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should create NEGs for all ports with the Ingress annotation, and NEGs for the standalone annotation otherwise(ingce-cos-master-ingress)[sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should be able to switch between HTTPS and HTTP2 modes(ingce-cos-1.14-ingress)
Since when has it been failing: late 2019-03-07
Testgrid link:
- https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-ingress
- https://testgrid.k8s.io/sig-release-1.14-blocking#gce-cos-1.14-ingress
Reason for failure: Timeout related to the L7 controller:
error: L7 controller failed to delete all cloud resources on time. timed out waiting for the condition
/sig network /priority critical-urgent (failing consistently in release blocking jobs, blocking other tests entirely from running)
cc @kubernetes/sig-network-test-failures cc @smourapina @alejandrox1 @kacole2 @mortent
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 31 (31 by maintainers)
All clear, closing.
/close
@mariantalla No this is a misunderstanding on my part with what this label meant. I thought it signified “open but unassigned” .
/remove-label triage/unresolved
@mariantalla ^^