Bug 1375932

Summary: It's better to show warning info when scaling failed due to restrictions
Product: OKD Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Jessica Forrester <jforrest>
Status: CLOSED CURRENTRELEASE QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: medium    
Version: 3.xCC: aos-bugs, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-09 21:50:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
AlwaysScaling none

Description Yadan Pei 2016-09-14 09:18:28 UTC 
Description of problem:
When scaling process failed due to resource restrictions, it will stop to create new pods, instead of always showing "scaling to 11...." it's better to give warning info telling quota/limit exceed

Version-Release number of selected component (if applicable):
openshift v1.3.0-rc1+7bb3e69
kubernetes v1.3.0+52492b4
etcd 2.3.0+git

How reproducible:
Always

Steps to Reproduce:
1.Create quota and limits for project "test"
# oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/project-quota/quota.yaml -n test
# oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/project-quota/limits.yaml -n test
2.Create DC for project "test"
# oc run testdc --image=aosqe/hello-openshift
3.Wait deployment complete
4.Scale DC
# oc scale dc/testdc --replicas=11
5.Check RC testdc-1 events on web console, after creating 7 pods, server could not create more pods since quota exceed
Error creating: pods "testdc-1-" is forbidden: Exceeded quota: quota, requested: memory=100Mi, used: memory=700Mi, limited: memory=750Mi 
6.Check pods on overview page

Actual results:
6. It keeps show "scaling to 11...." in pod donut text

Expected results:
6. Since no more pods could be created due to quota restrictions, it's better to give warning info telling quota exceed instead of always showing "scaling to 11...."

Additional info:
Comment 1 Yadan Pei 2016-09-14 09:19:07 UTC 
Created attachment 1200764 [details]
AlwaysScaling
Comment 2 Jessica Forrester 2016-11-08 14:52:24 UTC 
With the quota warnings we did this release we have fixed this issue.
Comment 3 Yadan Pei 2016-11-10 07:01:23 UTC 
Only one Resource type is used up, a quota warning will be displayed

If requested resource is larger than remaining quota, it still show "scaling to 11..." although pods will not be created, after talking with yanpzhan, I got to know this is working by design, so move to VERIFIED