kubernetes: [Failing Test] sig-network-ingress-gce

Which test(s) are failing:

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should support multiple TLS certs

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] multicluster ingress should get instance group annotation

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should conform to Ingress spec

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:Ingress] should create ingress with pre-shared certificate

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] rolling update backend pods should not cause service disruption

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to create a ClusterIP service

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should be able to switch between IG and NEG modes

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should conform to Ingress spec

  • [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

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints for both Ingress-referenced NEG and standalone NEG

  • [sig-network] Loadbalancing: L7 GCE [Slow] [Feature:NEG] should sync endpoints to NEG

Since when has it been failing: The full testgrid history is red, but it has been failing at least since 5/29

Testgrid link:

https://testgrid.k8s.io/sig-network-ingress-gce-e2e#ingress-gce-e2e&width=5

Reason for failure:

FAIL: error in waiting for ingress to get an address: Ingress failed to acquire an IP address within 10m0s

Anything else we need to know:

Originally these failures were due to an rbac permission issue (see: #93031), but now that that has been resolved, the tests are still not passing.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 19 (17 by maintainers)

Most upvoted comments

@spencerhance @liggitt Hi, I’ve filed #95025 to address the issue.

/cc @spencerhance

did ingress-gce just start expecting access to this resource recently? does the RBAC role at https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/rbac/cluster-loadbalancing/glbc/roles.yaml#L13-L18 need to be updated?

Also assigning @spencerhance since I think he’s already looking into this: /assign @spencerhance