-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.15.z
-
None
-
No
-
False
-
Description of problem:
test_scale_down_to_0_nodepool fails on CI on 4.15
Version-Release number of selected component (if applicable):
[kni@ocp-edge119 ~]$ oc version Client Version: 4.14.14 Kustomize Version: v5.0.1 Server Version: 4.15.0-0.nightly-2024-05-04-030917 Kubernetes Version: v1.28.9+8ca71f7 [kni@ocp-edge119 ~]$ /var/lib/jenkins/workspace/ocp-hypershift-cnv/clusterconfigs/hypershift -v hypershift version openshift/hypershift: afd03b2c9e3d0db1bc7274e554dde5da970bf21b. Latest supported OCP: 4.15.0 [kni@ocp-edge119 ~]$ oc get nodepool hyper-1 -n clusters --kubeconfig ~/clusterconfigs/auth/hub-kubeconfig -o wide NAME CLUSTER DESIRED NODES CURRENT NODES AUTOSCALING AUTOREPAIR VERSION UPDATINGVERSION UPDATINGCONFIG MESSAGE hyper-1 hyper-1 0 2 False False 4.15.12 [kni@ocp-edge119 ~]$
How reproducible:
100%
Steps to Reproduce:
1. deploy a hub cluster with hypershift kubevirt provider (I used this jo
*https://auto-jenkins-csb-kniqe.apps.ocp-c1.prod.psi.redhat.com/job/CI/job/job-runner/2757/*
)
2. run test_scale_down_to_0_nodepool and see it fail to reach 0 nodes (I used this job for that : https://auto-jenkins-csb-kniqe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-edge-auto-tests/13685/ )
3.
Actual results:
wont get to 0 nodes in the nodepool
Expected results:
a nodepool with 0 nodes is supported
Additional info:
