-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.16.0
-
+
-
No
-
3
-
ShiftStack Sprint 254
-
1
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
Autoscaler should use a ClusterAutoscaler that has 100 maximum total nodes count It scales from/to zero
Version-Release number of selected component (if applicable):
How reproducible:
All platforms are failing with the same issue. https://prow.ci.openshift.org/?job=periodic-ci-openshift-cluster-api-actuator-pkg-master-e2e-*-operator-periodic
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
Our scale from zero code is here: https://github.com/openshift/machine-api-provider-openstack/blob/bf45c1fb232122e978eb73336be6d5e441c41d9d/pkg/machineset/controller.go#L87-L127 This comes from this PR. Looks like it was only tested on presubmits but the tests are periodic only. https://github.com/openshift/cluster-api-actuator-pkg/pull/312/
- depends on
-
OCPBUGS-33974 CAO not finding new upstream annotations on MachineSet as they're not being added in time due to a race condition
- Closed