Description of problem: After create app with cpu limits set on web console, on dc page click "Add autoscaler" to create hpa, it always show warning info "This deployment config does not have any containers with a CPU request set. Autoscaling will not work without a CPU request." In fact, containers will have cpu requests set as cpu limits automatically, and autoscaling can work. Version-Release number of selected component (if applicable): OpenShift v3.3.0.14 Kubernetes v1.3.0+57fb9ac How reproducible: Always Steps to Reproduce: Metrics is deployed in advance. 1.Create app from image with cpu limits set on web console. 2.Click "Add autoscaler" to create hpa on dc page. 3.Check dc page after hpa was created. Actual results: 1.App is created successfully 2.Show warning info on hpa creation page:"This deployment config does not have any containers with a CPU request set. Autoscaling will not work without a CPU request." , and could create hpa successfully. 3.There is also warning info: "This deployment config does not have any containers with a CPU request set. Autoscaling will not work without a CPU request. Set resource requests and limits" Expected results: 2,3, Should no warning info. Additional info:
Created attachment 1187733 [details] create-hpa
Created attachment 1187734 [details] after-create-hpa
https://github.com/openshift/origin-web-console/pull/301
merging to origin in https://github.com/openshift/origin/pull/10253
sorry forgot this was an OCP bug, leaving as assigned to origin PR merges
Tested on openshift v3.3.0.18. After create app with cpu limits set on web console, when create hpa or after created hpa, will not show warning info about no cpu request now. The bug has been fixed, so move it to Verified.