kubernetes: [e2e failure] [sig-autoscaling] [HPA] Horizontal pod autoscaling (scale resource: CPU) [sig-autoscaling] [Serial] [Slow] ReplicaSet Should scale ...

/priority critical-urgent /sig autoscaling

This test case started failing recently and affects a number of jobs: triage report

This is affecting multiple jobs on the release-master-blocking testgrid dashboard, and prevents us from cutting 1.9.0-alpha.2 (kubernetes/sig-release#22). Is there work ongoing to bring this job back to green?

triage cluster b75045e2cb613e12dca1

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/horizontal_pod_autoscaling.go:39
timeout waiting 15m0s for 5 replicas
Expected error:
    <*errors.errorString | 0xc4202cafe0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/horizontal_pod_autoscaling.go:128

Suspect range from gci-gce-serial: https://github.com/kubernetes/kubernetes/compare/060b4b8b8...51244eb0f

Suspect range from gci-gke-serial: https://github.com/kubernetes/kubernetes/compare/b1e2d7a9d...82a52a901

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 29 (29 by maintainers)

Commits related to this issue

Most upvoted comments

@DirectXMan12 the moment this test started failing coincides exactly with merging of https://github.com/kubernetes/kubernetes/pull/53743. Which BTW is a very large commit to HPA which was not tagged with sig-autoscaling and therefore slipped us completely.

I think we should revert #53743 for now and merge it again after fixing it.

cc: @mwielgus