-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.17
-
Moderate
-
Yes
-
False
-
-
-
Release Note Not Required
-
In Progress
Description of problem:
Autoscaler balance similar node groups failed on aws when run regression for https://issues.redhat.com/browse/OCPCLOUD-2616
Version-Release number of selected component (if applicable):
4.17.0-0.nightly-2024-06-20-165244
How reproducible:
Always
Steps to Reproduce:
1. Create clusterautoscaler with balanceSimilarNodeGroups: true 2. Create 2 machineautoscaler min/max 1/8 3. Add workload
Actual results:
Couldn't see the "splitting scale-up" message from the cluster-autoscalerlogs. must-gather: https://drive.google.com/file/d/17aZmfQHKZxJEtqPvl37HPXkXA36Yp6i8/view?usp=sharing 2024-06-21T13:21:08.678016167Z I0621 13:21:08.678006 1 compare_nodegroups.go:157] nodes template-node-for-MachineSet/openshift-machine-api/zhsun-aws21-5slwv-worker-us-east-2b-5109433294514062211 and template-node-for-MachineSet/openshift-machine-api/zhsun-aws21-5slwv-worker-us-east-2c-760092546639056043 are not similar, labels do not match 2024-06-21T13:21:08.678030474Z I0621 13:21:08.678021 1 orchestrator.go:249] No similar node groups found
Expected results:
balanceSimilarNodeGroups works well
Additional info:
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update