Skip to content

flaky/broken e2e: Services should be able to change the type and nodeport settings of a service #13818

Closed
@j3ffml

Description

Test is failing pretty regularly at the same point; after updating service nodeport, it expects the loadbalancer ingress to be the same as before, but this is not the case:

• Failure [262.469 seconds]
Services
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:967
  should be able to change the type and nodeport settings of a service [It]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:650

  Expected
      <api.LoadBalancerIngress>: {IP: "104.154.44.93", Hostname: ""}
  to equal
      <api.LoadBalancerIngress>: {IP: "104.197.22.89", Hostname: ""}

  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:608

Not familiar with loadbalancer creation code, so not sure whether test or service controller is broken. If we expect the loadbalancer ingress ip to be the same after updating the nodeport, this would indicate a bug in the service controller.

cc @justinsb @ArtfulCoder

Metadata

Assignees

Labels

kind/flakeCategorizes issue or PR as related to a flaky test.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions