Openshift:没有可用节点与以下所有谓词匹配:: CPU不足(173)，MatchNodeSelector(5) [英] Openshift: No nodes are available that match all of the following predicates:: Insufficient cpu (173), MatchNodeSelector (5)

问题描述

我在West-1的Openshift v3上有一个项目.在其中，我有一个运行良好的应用程序，而在GitHub在代码中向下游提交某些内容后，该应用程序停止了工作.问题在于制作吊舱:

I have a project in west-1 on Openshift v3. In it I have an app that worked fine and one that stopped working following a GitHub committing something very downstream within the code. The issue is with making a pod:

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

我停止了它，然后按比例缩小了另一个Pod，以查看是否是另一个怪异的设置，而其他人的新构建可能也没有得到，但我得到了相同的结果.现在都坏了.
是Red Hat Openshift的CPU用完了还是我有一些奇怪的默认设置决定请求173个CPU和5个节点?

I stopped it and then I scaled down the other pod to see if it was any weird settings that the new build for the other might have picked up and I get the same. Now both are broken.
Is it that Red Hat Openshift has run out of CPUs or have I got some weird default setting that has decided to request 173 CPUs and 5 Nodes?

推荐答案

该消息并不表示Pod正在请求173个CPU.

The message doesn't mean that the pod is requesting 173 CPUs.

该错误消息表示调度失败，原因是在173台计算机上没有足够的CPU可用空间来满足pod请求(请参阅pod定义)，在5台计算机(节点)上无法调度，因为这些节点没有不能在 spec.nodeSelector 的Pod定义. (两组节点之间可能有交集)

The error message means that scheduling failed that on 173 machines there isn't enough CPU left available to fit the pod requests (see pod definition) and on 5 machines (nodes) it can't be scheduled because those nodes don't have the particular set of labels the pod is specifying in spec.nodeSelector of the pod definition. (There might be intersection between the 2 groups of nodes)

这篇关于Openshift:没有可用节点与以下所有谓词匹配:: CPU不足(173)，MatchNodeSelector(5)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！