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

Deployment cannot be scaled up/down from GUI when an HPA is associated with it.

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.16.0
    • 4.12, 4.15
    • Management Console
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, a deployment could not be scaled up or down when a `HorizontalPodAutoscaler` is present. With this update, when a deployment with an `HorizontalPodAutoscaler` is scaled down to `zero`, an *Enable Autoscale* button is displayed so you can enable pod autoscaling. (link:https://issues.redhat.com/browse/OCPBUGS-22405[*OCPBUGS-22405*])
      Show
      * Previously, a deployment could not be scaled up or down when a `HorizontalPodAutoscaler` is present. With this update, when a deployment with an `HorizontalPodAutoscaler` is scaled down to `zero`, an *Enable Autoscale* button is displayed so you can enable pod autoscaling. (link: https://issues.redhat.com/browse/OCPBUGS-22405 [* OCPBUGS-22405 *])
    • Bug Fix
    • Done

      Description of problem:

      Deployment cannot be scaled up/down when an HPA is associated with it.

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

      4.12

      How reproducible:

      100%

      Steps to Reproduce:

      1. Create a test deployment
      $ oc new-app httpd
      2. Create a HPA for the deployment
      $ oc autoscale deployment/httpd --min 1 --max 10 --cpu-percent 10 
      3. Scale down the deployment via script or manually to 0 replicas.
      $ oc scale deployment/httpd --replicas=0
      4. The HPA shows below status that it cannot scale up until the deployment is scaled up.
      ~~~
           - type: ScalingActive
            status: 'False'
            lastTransitionTime: '2023-10-24T10:00:01Z'
            reason: ScalingDisabled
            message: scaling is disabled since the replica count of the target is zero
      ~~~  
      5. Since the scale up/down is disabled, the users will not be able to scale up the deployment from GUI. The only option is to do it from CLI.

      Actual results:

      The scale up/down arrows are disabled and users are unable to start the deployment.

      Expected results:

      The scale up/down arrows should be enabled or another option that can help to scale up the deployment.

      Additional info:

       

            [OCPBUGS-22405] Deployment cannot be scaled up/down from GUI when an HPA is associated with it.

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:0041

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:0041

            Xiyun Zhao added a comment -

            This bug has been verified on the payload 4.16.0-0.nightly-2024-04-23-032717
            Verification Step follows the step in the description
            Result: When a deployment, with HPA, has been scaled down to zero, a new button 'Enable Autoscale' is displayed to help user scale up the deployment automatically.

            Xiyun Zhao added a comment - This bug has been verified on the payload 4.16.0-0.nightly-2024-04-23-032717 Verification Step follows the step in the description Result: When a deployment, with HPA, has been scaled down to zero, a new button 'Enable Autoscale' is displayed to help user scale up the deployment automatically.

            Hi sgoodwin_redhat,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi sgoodwin_redhat , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            Hello Team,

            Could you please provide any update ?

            Deepesh Sharma added a comment - Hello Team, Could you please provide any update ?

            Arpitha DV added a comment -

            Could you please provide any update ?

            Arpitha DV added a comment - Could you please provide any update ?

              sgoodwin_redhat Steve goodwin
              rhn-support-pkhilare Pawan Khilare
              Xiyun Zhao Xiyun Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: