Openshift: there are no nodes available that match all of the following predicates: Not enough cpu (173), MatchNodeSelector (5)

Question

I have a project in West-1 on Openshift v3. In it, I have an application that works fine, and one that stops working after GitHub does something very bad in the code. The problem is creating the container:

No nodes are available that match all of the following predicates:: Insufficient cpu (173), MatchNodeSelector (5). 

I stopped it, and then I reduced the size of the other container to see if there were any strange settings that the new assembly for another could pick up, and I get the same. Now both are broken.
Does Red Hat Openshift run out of processors or do I have some weird default settings that decide to request 173 processors and 5 nodes?

Answer 1

The message does not mean that the module is requesting 173 CPUs.

The error message means that planning failed, that for 173 machines there is not available there to match the pod requests, enough CPU (see cm pod definition) and for 5 machines (nodes) cannot be scheduled because these nodes don’t have a specific set of pod labels with specifying the spec.nodeSelector definition in spec.nodeSelector . (There may be an intersection between two groups of nodes)