Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-31875

Disabling nodepool autoscaling by setting an explicit scale on kubevirt provider hosted cluster, is not blocked as for agent provider

XMLWordPrintable

    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          on a nodepool with (kubevirt provider) Autoscaling Enabled, "oc scale nodepool" command is disabling Autoscaling, but leaves an invalid configuration with Autoscaling info that should have been cleared. 

      Version-Release number of selected component (if applicable):

         (.venv) [kni@ocp-edge119 ocp-edge-auto_cluster]$ oc version
      Client Version: 4.14.14
      Kustomize Version: v5.0.1
      Server Version: 4.14.20
      Kubernetes Version: v1.27.11+ec42b99
      (.venv) [kni@ocp-edge119 ocp-edge-auto_cluster]$ ~/hypershift_working/hypershift/bin/hcp -v
      hcp version openshift/hypershift: 02158e2caf8f5f0efc574c4f13ae60b0c36cf7af. Latest supported OCP: 4.16.0
      (.venv) [kni@ocp-edge119 ocp-edge-auto_cluster]$ 
       

      How reproducible:

            happens all the time  
      

      Steps to Reproduce:

      The detailed steps & fix are in this ticket, seems the fix is working for agent provider only, should behave the same for all providers.
      
      on kubevirt cluster :
       [kni@ocp-edge119 ocp-edge-auto_cluster]$ oc get nodepool -A -o wide --kubeconfig ~/clusterconfigs/auth/hub-kubeconfig
      NAMESPACE   NAME      CLUSTER   DESIRED NODES   CURRENT NODES   AUTOSCALING   AUTOREPAIR   VERSION   UPDATINGVERSION   UPDATINGCONFIG   MESSAGE
      clusters    hyper-1   hyper-1                   1               True          False        4.14.20                                      Minimum availability requires 2 replicas, current 1 available
      
      [kni@ocp-edge119 ocp-edge-auto_cluster]$ oc scale nodepool/hyper-1 --namespace clusters --kubeconfig ~/clusterconfigs/auth/hub-kubeconfig --replicas=4
      nodepool.hypershift.openshift.io/hyper-1 scaled
      
      
      

      Actual results:

      nodepool.hypershift.openshift.io/hyper-1 scaled
         

      Expected results:

      scaling when autoscaling is enabled is no permitted because it results in a none valid configuration.     

      Additional info:

          Relates to this fix that covers agent provider, should be implemented for all providers the same:
      https://issues.redhat.com/browse/OCPBUGS-30930
      
      
      
      

            rhn-engineering-dvossel David Vossel
            rhn-support-gamado Gal Amado
            Liangquan Li Liangquan Li
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: