-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-63339. The following is the description of the original issue:
—
Description of problem:
Horizontal Pod Autoscaler (HPA) section incorrectly mandates that both CPU Utilization and Memory Utilization metrics be specified. Users are not able to configure an HPA with only one of these resource metrics. F urthermore, if a user removes one of the metrics via the YAML view, the form view repopulates both fields upon re-editing, ignoring the actual configuration. YAML config works fine however, Web Console Form View does not refelect the YAML config correctly if any of the metrics is skipped.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Workloads > Deployment/DeploymentConfig > Create Deployment/DeploymentConfig 2. From Deployment/DeploymentConfig -> Add HorizontalPodAutoscaler -> Form View -> Both CPU Utilization and Memory Utilization are mandatory. No way to skip using either of the resource metric.when setting the utilization value to 0, it gives following message: Error "Invalid value: 0: must be greater than 0" for field "spec.metrics[1].resource.target.averageUtilization". Same with Edit edit option.
Actual results:
Gives error and no way to skip.
Expected results:
HPA form view should allow the user to configure an HPA based on a single resource metric (either CPU or Memory) without requiring the other.
Additional info:
- clones
-
OCPBUGS-63339 HPA Form View in RHOCP Web Console Incorrectly Requires Both CPU and Memory Metrics
-
- MODIFIED
-
- is blocked by
-
OCPBUGS-63339 HPA Form View in RHOCP Web Console Incorrectly Requires Both CPU and Memory Metrics
-
- MODIFIED
-
- links to