cluster-api-provider-aws: [E2E] Tests for MachinePool failing in open PRs

/kind bug

What steps did you take and what happened: E2E tests for machinepools failing with below error

E0309 08:38:12.873061 1 awsmachinepool_controller.go:254] “msg”=“error updating AWSMachinePool” “error”=“unable to update ASG: failed to update ASG "machine-pool-oxhbj8-mp-0": ValidationError: Desired capacity:0 must be between the specified min size:1 and max size:4\n\tstatus code: 400, request id: 7a81e62c-9a96-4824-8510-69432b30f83c”

What did you expect to happen: E2E tests should pass

Anything else you would like to add: Probably happened because of https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/3255

Environment:

Cluster-api-provider-aws version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 15 (15 by maintainers)

Most upvoted comments

@shivi28 Do you know why not allowing scale to 0 caused e2e test failures only during upgrade? Was there a change in the cluster-api e2e tests we use?

Yes @sedefsavas they have added a new test case Scaling the machine pool to zero in CAPI e2e test

shivi28 on Mar 15, 2022