<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):<br>
failed to fit in any node Insufficient CPU<br>
scheduler and other</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):<br>
BUG</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;3&quot;, GitVersion:&quot;v1.3.7&quot;, GitCommit:&quot;a2cba278cba1f6881bb0a7704d9cac6fca6ed435&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-09-12T23:15:30Z&quot;, GoVersion:&quot;go1.6.2&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;3&quot;, GitVersion:&quot;v1.3.7&quot;, GitCommit:&quot;a2cba278cba1f6881bb0a7704d9cac6fca6ed435&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-09-12T23:08:43Z&quot;, GoVersion:&quot;go1.6.2&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}"><pre class="notranslate"><code class="notranslate">Client Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.7", GitCommit:"a2cba278cba1f6881bb0a7704d9cac6fca6ed435", GitTreeState:"clean", BuildDate:"2016-09-12T23:15:30Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.7", GitCommit:"a2cba278cba1f6881bb0a7704d9cac6fca6ed435", GitTreeState:"clean", BuildDate:"2016-09-12T23:08:43Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}
</code></pre></div>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: AWS</li>
<li><strong>OS</strong> (e.g. from /etc/os-release):</li>
</ul>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="NAME=&quot;Ubuntu&quot;
VERSION=&quot;14.04.1 LTS, Trusty Tahr&quot;
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=&quot;Ubuntu 14.04.1 LTS&quot;
VERSION_ID=&quot;14.04&quot;
HOME_URL=&quot;http://www.ubuntu.com/&quot;
SUPPORT_URL=&quot;http://help.ubuntu.com/&quot;
BUG_REPORT_URL=&quot;http://bugs.launchpad.net/ubuntu/&quot;"><pre class="notranslate"><code class="notranslate">NAME="Ubuntu"
VERSION="14.04.1 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.1 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
</code></pre></div>
<ul dir="auto">
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>):</li>
</ul>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Linux prod-kube-master-01 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"><pre class="notranslate"><code class="notranslate">Linux prod-kube-master-01 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
</code></pre></div>
<ul dir="auto">
<li><strong>Install tools</strong>:<br>
only kubernetes componenet and docker<br>
kubectl, kuberentesa-apiserver ,kubelet ,kube-scheduler</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
rolling-update is not working. after checking kubectl events find out it is giving below error</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="9m        1d        107       xxxx-916abedbd8771c69102548f7167bf9b7-4snr0   Pod                 Warning   FailedScheduling   {default-scheduler }   pod (xxx-916abedbd8771c69102548f7167bf9b7-4snr0) failed to fit in any node
fit failure on node (prod-kube-minion-02): Insufficient CPU
fit failure on node (prod-kube-minion-04): Insufficient CPU
fit failure on node (prod-kube-minion-03): Insufficient CPU
fit failure on node (prod-kube-minion-01): Insufficient CPU"><pre class="notranslate"><code class="notranslate">9m        1d        107       xxxx-916abedbd8771c69102548f7167bf9b7-4snr0   Pod                 Warning   FailedScheduling   {default-scheduler }   pod (xxx-916abedbd8771c69102548f7167bf9b7-4snr0) failed to fit in any node
fit failure on node (prod-kube-minion-02): Insufficient CPU
fit failure on node (prod-kube-minion-04): Insufficient CPU
fit failure on node (prod-kube-minion-03): Insufficient CPU
fit failure on node (prod-kube-minion-01): Insufficient CPU
</code></pre></div>
<p dir="auto">it is not giving any information about usage in the above message (available and requested cpu)<br>
i have checked other things like memory and hard-disk anf there is no issue with them more then 80% of mem and cpu are free</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Name:           prod-kube-minion-04
Labels:         beta.kubernetes.io/arch=amd64
            beta.kubernetes.io/os=linux
            kubernetes.io/hostname=prod-kube-minion-04
Taints:         &lt;none&gt;
CreationTimestamp:  Tue, 04 Oct 2016 13:17:48 +0530
Phase:
Conditions:
  Type          Status  LastHeartbeatTime           LastTransitionTime          Reason              Message
  ----          ------  -----------------           ------------------          ------              -------
  OutOfDisk         False   Mon, 17 Oct 2016 10:59:22 +0530     Tue, 04 Oct 2016 13:42:52 +0530     KubeletHasSufficientDisk    kubelet has sufficient disk space available
  MemoryPressure    False   Mon, 17 Oct 2016 10:59:22 +0530     Tue, 04 Oct 2016 13:17:48 +0530     KubeletHasSufficientMemory  kubelet has sufficient memory available
  Ready         True    Mon, 17 Oct 2016 10:59:22 +0530     Tue, 04 Oct 2016 13:42:52 +0530     KubeletReady            kubelet is posting ready status
Addresses:      10.70.43.72,10.70.43.72
Capacity:
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   8
 memory:                32948064Ki
 pods:                  110
Allocatable:
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   8
 memory:                32948064Ki
 pods:                  110
System Info:
 Machine ID:            1567d6e82a6770a1b07ff67b5426933c
 System UUID:           EC20081E-60CF-FC0D-A3FC-52D37B90A9ED
 Boot ID:           61d04907-77b7-4106-b32e-dbad8ae48879
 Kernel Version:        3.13.0-36-generic
 OS Image:          Ubuntu 14.04.1 LTS
 Operating System:      linux
 Architecture:          amd64
 Container Runtime Version: docker://1.11.0
 Kubelet Version:       v1.3.7
 Kube-Proxy Version:        v1.3.7
ExternalID:         prod-kube-minion-04
Non-terminated Pods:        (11 in total)
  Namespace         Name                                    CPU Requests    CPU Limits  Memory Requests Memory Limits
  ---------         ----                                    ------------    ----------  --------------- -------------
xxx
xxx
xxx
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted. More info: http://releases.k8s.io/HEAD/docs/user-guide/compute-resources.md)
  CPU Requests  CPU Limits  Memory Requests Memory Limits
  ------------  ----------  --------------- -------------
  4260m (53%)   0 (0%)      15840Mi (49%)   15840Mi (49%)"><pre class="notranslate"><code class="notranslate">Name:           prod-kube-minion-04
Labels:         beta.kubernetes.io/arch=amd64
            beta.kubernetes.io/os=linux
            kubernetes.io/hostname=prod-kube-minion-04
Taints:         &lt;none&gt;
CreationTimestamp:  Tue, 04 Oct 2016 13:17:48 +0530
Phase:
Conditions:
  Type          Status  LastHeartbeatTime           LastTransitionTime          Reason              Message
  ----          ------  -----------------           ------------------          ------              -------
  OutOfDisk         False   Mon, 17 Oct 2016 10:59:22 +0530     Tue, 04 Oct 2016 13:42:52 +0530     KubeletHasSufficientDisk    kubelet has sufficient disk space available
  MemoryPressure    False   Mon, 17 Oct 2016 10:59:22 +0530     Tue, 04 Oct 2016 13:17:48 +0530     KubeletHasSufficientMemory  kubelet has sufficient memory available
  Ready         True    Mon, 17 Oct 2016 10:59:22 +0530     Tue, 04 Oct 2016 13:42:52 +0530     KubeletReady            kubelet is posting ready status
Addresses:      10.70.43.72,10.70.43.72
Capacity:
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   8
 memory:                32948064Ki
 pods:                  110
Allocatable:
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   8
 memory:                32948064Ki
 pods:                  110
System Info:
 Machine ID:            1567d6e82a6770a1b07ff67b5426933c
 System UUID:           EC20081E-60CF-FC0D-A3FC-52D37B90A9ED
 Boot ID:           61d04907-77b7-4106-b32e-dbad8ae48879
 Kernel Version:        3.13.0-36-generic
 OS Image:          Ubuntu 14.04.1 LTS
 Operating System:      linux
 Architecture:          amd64
 Container Runtime Version: docker://1.11.0
 Kubelet Version:       v1.3.7
 Kube-Proxy Version:        v1.3.7
ExternalID:         prod-kube-minion-04
Non-terminated Pods:        (11 in total)
  Namespace         Name                                    CPU Requests    CPU Limits  Memory Requests Memory Limits
  ---------         ----                                    ------------    ----------  --------------- -------------
xxx
xxx
xxx
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted. More info: http://releases.k8s.io/HEAD/docs/user-guide/compute-resources.md)
  CPU Requests  CPU Limits  Memory Requests Memory Limits
  ------------  ----------  --------------- -------------
  4260m (53%)   0 (0%)      15840Mi (49%)   15840Mi (49%)
</code></pre></div>
<p dir="auto">every other node have free resource according to kubectl describe node<br>
and i am facing this issue with every other app as well<br>
i have brought a new node and rolling-update works fine so its not pod which is requesting more cpu then node have</p>
<p dir="auto">this is the resource limit i have given to every app</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="         resources:
           limits:
             memory: 1500Mi
           requests:
             cpu: 420m"><pre class="notranslate"><code class="notranslate">         resources:
           limits:
             memory: 1500Mi
           requests:
             cpu: 420m
</code></pre></div>
<p dir="auto">and i think it should give usage in error msg as well.</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
i have expected it to deploy successfully as every node have sufficient cpu,disk and memory</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:<br>
i have upgraded my kuberentes 2 weeks back to 1.3.7 so it may be problem in this version</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.): No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.): fialed</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one): BUG REPORT</p>
<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>): Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:16:57Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: local VirtualBox machines managed with Vagrant</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): Ubuntu 16.04 (both host and VMs)</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): Linux kubenode01 4.4.0-38-generic <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35453339" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/57" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kubernetes/pull/57/hovercard" href="https://github.com/kubernetes/kubernetes/pull/57">#57</a>-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux</li>
<li><strong>Install tools</strong>: kubeadm</li>
<li><strong>Others</strong>: Vagrant</li>
</ul>
<p dir="auto"><strong>What happened</strong>: I'm testing a Kubernetes cluster with VirtualBox and Vagrant. Every VM has an NATed interface (eth0) and a Host-Only interface (eth1). I wanted to make the first node try to join the master using the Host-Only IP address because Kubernetes is listening on all interfaces by default.</p>
<p dir="auto"><strong>What you expected to happen</strong>: Since the master is listening to all interfaces available, I was expecting it to just work.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible): Setup two VMs, with one NATed interface, and one Host-Only interface. Follow steps from <a href="http://kubernetes.io/docs/getting-started-guides/kubeadm/" rel="nofollow">http://kubernetes.io/docs/getting-started-guides/kubeadm/</a> but instead of using exactly the <code class="notranslate">kubeadm join ...</code> command-line returned by the master, change the IP address to the one of the Host-Only interface.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>: You can use this to reproduce the issue: <a href="https://github.com/hgfischer/Kubernetes14">https://github.com/hgfischer/Kubernetes14</a></p>