-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.12, 4.15
-
None
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:
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update
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