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
https://github.com/openshift/origin-web-console/pull/1612
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/8b08dba85b63e52440072641438c4cd297df3d91 Bug 1455105 - Correct quota / HPA donut warnings Consistently show the same quota and HPA warnings everywhere we show the pod donut. Fixes an issue where we would incorrectly show an HPA warning when cluster resource overrides were enabled on the deployment page. Also adds quota warnings to the donut on other pages, not just the overview.
Tested this bug against online free-int cluster, it was fixed. version: v3.6.116 (online version 3.5.0.20)
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