In some cases, the web console replication controller and replica set pages incorrectly warned that a container did not have a CPU request set, preventing autoscaling from working. The web console was not correctly applying the limit range default for CPU request when detecting this warning.
The web console has been fixed on these pages to correctly apply the limit range default, so there is no warning about CPU request when a horizontal pod autoscaler is enabled.
Created attachment 1281904[details]
warning
Description of problem:
After creating HPA without setting resources limits manually, rc/dc etc page will have yellow icon which warns (overview page has no the yellow icon, though): This replication controller does not have any containers with a CPU limit set. Autoscaling will not work without a CPU limit. The CPU limit will be automatically calculated from the container memory.
In OCP it is normal, but in Online, this warning is not needed, because Online has ClusterResourceOverride configuration which will automatically enforce resource limit on rc/dc etc.
Version-Release number of selected component (if applicable):
OpenShift Master:v3.5.5.16 (online version 3.5.1.12)
Kubernetes Master:v1.5.2+43a9be4
How reproducible:
Always
Steps to Reproduce:
1.Login in web console against the online env.
2.Create rc
# oc run myrun-rc --image=yapei/hello-openshift --generator=run-controller/v1
3.Create HPA from the replication controller page
Add name,Min replicas(2),Max replicas(10),Target CPU Utilization
4. Check the replication controller page
Actual results:
4.There is text "Autoscaled min:2, max:10" besides warning sign under deployment pod(see attachment)
Expected results:
4. should not display the warning sign
Additional info:
1.see same issues on other online clusters
2.There is no warning sign under pods-donut on overview page
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, 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/RHEA-2017:1716
Created attachment 1281904 [details] warning Description of problem: After creating HPA without setting resources limits manually, rc/dc etc page will have yellow icon which warns (overview page has no the yellow icon, though): This replication controller does not have any containers with a CPU limit set. Autoscaling will not work without a CPU limit. The CPU limit will be automatically calculated from the container memory. In OCP it is normal, but in Online, this warning is not needed, because Online has ClusterResourceOverride configuration which will automatically enforce resource limit on rc/dc etc. Version-Release number of selected component (if applicable): OpenShift Master:v3.5.5.16 (online version 3.5.1.12) Kubernetes Master:v1.5.2+43a9be4 How reproducible: Always Steps to Reproduce: 1.Login in web console against the online env. 2.Create rc # oc run myrun-rc --image=yapei/hello-openshift --generator=run-controller/v1 3.Create HPA from the replication controller page Add name,Min replicas(2),Max replicas(10),Target CPU Utilization 4. Check the replication controller page Actual results: 4.There is text "Autoscaled min:2, max:10" besides warning sign under deployment pod(see attachment) Expected results: 4. should not display the warning sign Additional info: 1.see same issues on other online clusters 2.There is no warning sign under pods-donut on overview page