oc v3.6.173.0.5

Steps to reproduce:
In namespace1
 - Create a PVC (make the PVC bind and work)
 - Create a pod using the PVC
 - Delete the PVC
 - Create a PVC with the same name, but this time make it such that it stay's pending forever (eg: ReadWriteMany on EBS)

In namespace2
 - create a valid PVC
 - create a valid Pod.

The namespace2 pod will be unable to schedule because:

https://github.com/kubernetes/kubernetes/blob/master/plugin/pkg/scheduler/algorithm/predicates/predicates.go#L284

will error out. filterVolumes() will iterate over all of the pods/PVCs on a node, will find namespace1 PVC by NAME, and will error when it find that it is pending. 

We then set the status on the 'namespace2' PVC to say something like:
  "message": "SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "namespace1PVC", which is unexpected."

This is bad since we leaked the PVC name from namespace1 into the status of a pod in namespace2.

This is also bad since we didn't schedule the namespace2 pod even though it could have been scheduled.


Description of problem:

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info: