Change:
Which jobs are failing:   Which test(s) are failing: The jobs are timing out, but just before that, the following tests failed: (in ) (in ) Since when has it been failing: late 2019-03-07 Testgrid link: Reason for failure: Timeout related to the L7 controller: /sig network /priority critical-urgent (failing consistently in release blocking jobs, blocking other tests entirely from running) cc cc
/milestone v1.14
could this be a gcp issue?
also cc'ing the sig-network chairs; could you help to triage this please?
Seems like Ingress controller kept panicing during the test (): /cc
Seems like has filed
this will likely mitigate the CI failures
Assigning to freehan and kubernetes/ingress-gce 's reviewer /assign
Can we move this to "Under investigation" on the CI project board?
^^
/triage unresolved
Hey I noticed the label - does that mean that it won't be resolved (as is documented ) or that it hasn't been yet?
No this is a misunderstanding on my part with what this label meant. I thought it signified "open but unassigned" . /remove-label triage/unresolved
/remove-triage unresolved triage labels seem to be a bit old, they should be revamped
and are still failing consistently, nearly all other are flaking frequently at the moment. /reopen
Reopened this issue. <detailsIn response to : Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
master-blocking runs are clearing out, but 1.14-blocking seem to still include the http2 test ( is the first that includes in )
Took a quick look, turned out job "ci-kubernetes-e2e-gce-cos-k8sbeta-ingress" doesn't skip test with the tag. The job config is auto-generated: or how can we add flag to that job?
hummmmmmm when did that tag becomes a thing?!
I think it is here We introduced that filter for Ingress-GCE tests only because we needed a way to turn off tests on specific branches.
Thanks both, let me send a PR to update that.
Why not use the feature tag? Introduce a new tag that need to be skipped by default will presumably break everything :-)
[feature:unreleased], instead of [unreleased]
That sounds like a reasonable approach, but it means we will need to update most of the ingress tests & jobs (more on-going PRs). Could we update that job to skip for now and file an issue to cleanup the tag after code freeze? ( Or maybe will happen first:) )
I have a feeling this unrelease tag is running in other jobs.. which branch has this tag?
The unrelease tag always co-presents with tag. So as long as we patch those ingress jobs it should be fine. is updating the remaining jobs: k8s-stable3 k8s-stable2 k8s-stable1 k8s-beta
+1 to MrHohn We have the filter on every job config. Each individual test has the unreleased tag based on what branch it needs to be tested on. So if none of the actual tests have "Unreleased" nothing gets skipped. Ref:
:+1:
that explains a lot of things 14-blocking is now starting to pass; with the https/http2 test removed: !
All clear, closing. /close
Closing this issue. <detailsIn response to : All clear, closing. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
// TODO(nikhiljindal): Check the instance group annotation value and verify with a multizone cluster. }) <del> It("should be able to switch between HTTPS and HTTP2 modes", func() { </del> <ins> // TODO: remove [Unreleased] tag to once the new GCE API GO client gets revendored in ingress-gce repo It("should be able to switch between HTTPS and HTTP2 modes [Unreleased]", func() { </ins> httpsScheme := "request_scheme=https" By("Create a basic HTTP2 ingress")