-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.17, 4.18
-
Moderate
-
Yes
-
CLOUD Sprint 260, CLOUD Sprint 261
-
2
-
False
-
-
-
-
Description of problem:
Once min-node is reached, the remain nodes' taints shouldn't have DeletionCandidateOfClusterAutoscaler
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-arm64-2024-09-13-023103
How reproducible:
Always
Steps to Reproduce:
1.Create ipi cluster 2.Create machineautoscaler and clusterautoscaler 3.Create workload so that , scaling would happen
Actual results:
DeletionCandidateOfClusterAutoscaler, taint are present even after min nodes are reached
Expected results:
above taints not present on nodes once min node count is reached
Additional info:
logs from the test - https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Runner/1037951/console
must-gather - https://drive.google.com/file/d/1zB2r-BRHjC12g17_Abc-xvtEqpJOopI5/view?usp=sharing
We did reproduce it manually and waited around 15 mins, taint was present.
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update