Description of problem:
free-stg cluster, pod always in Pending status, info shows "0/27 nodes are available: 1 node(s) were not ready, 11 node(s) didn't match node selector, 15 Insufficient cpu"

$ oc get pod
NAME              READY     STATUS    RESTARTS   AGE
ruby-ex-1-build   0/1       Pending   0          21h


$ oc describe pod ruby-ex-1-build
Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  3m (x4432 over 21h)  default-scheduler  0/27 nodes are available: 1 node(s) were not ready, 11 node(s) didn't match node selector, 15 Insufficient cpu.


Version-Release number of selected component (if applicable):
OpenShift Master:v3.10.27 
Kubernetes Master:v1.10.0+b81c8f8 
OpenShift Web Console:v3.10.27 

How reproducible:
Always

Steps to Reproduce:
1. oc new-project ruby; 
2. oc new-app centos/ruby-25-centos7~https://github.com/sclorg/ruby-ex.git
3.

Actual results:
pod always in Pending status

Expected results:
pod could be started up

Additional info: