Description of problem:
When pod without request value, it still can be scheduled to node which "allocatable" value is 0.
Even there is another node has enough "allocatable" resouce, it sometime still can be scheduled to the node which "allocatable" value is 0
http://pastebin.test.redhat.com/359139

Version-Release number of selected component (if applicable):
openshift v3.2.0.6
kubernetes v1.2.0-36-g4a3f9c5
etcd 2.2.5

How reproducible:
Always

Steps to Reproduce:
1.Set node reserved to equal node's capacity
kubeletArguments:
  system-reserved:
    - "cpu=1,memory=2G"
  kube-reserved:
    - "cpu=1,memory=2G"

2.Check node allocatable
"allocatable": {
    "cpu": "0",
    "memory": "0",
    "pods": "110"
}

3.Create a pod without request
$ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/hello-openshift/hello-pod.json

4.Check pod status

Actual results:
4.It's running and be scheduled to node which cpu and memory is 0.

Expected results:
4.The pod should pending.

Additional info: