Bug 1617928

Summary:	[online-int][online-stg]The pod cannot be deployed as the reason of "Failed Scheduling"
Product:	OpenShift Online	Reporter:	wangyu <yuwan>
Component:	Website	Assignee:	Abhishek Gupta <abhgupta>
Status:	NEW ---	QA Contact:	wangyu <yuwan>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.x	CC:	aos-bugs
Target Milestone:	---	Keywords:	OnlinePro
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:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description wangyu 2018-08-16 07:33:24 UTC

Description of problem:
The pod cannot be deployed as the reason of "Failed Scheduling".
The error message is as bellow:
"0/9 nodes are available: 1 NodeNotReady, 1 NodeOutOfDisk, 3 Insufficient cpu, 5 MatchNodeSelector."

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.Log in openshift web console 
2.Create a new project 
# oc new-projet test
3.Create one app with pod.
#oc new-app centos/ruby-22-centos7~https://github.com/openshift/ruby-ex.git

Actual results:
3.The pod fails to be created with the above error.

Expected results:
3.The pod should be created successfully.

Additional info: