Daemonset can not create the needed pod when the node has enough resource after the other daemonset delete

[chentao1596]

What happened:
I create two daemonsets, only one can create the needed pod because of the node's resource is not enough.
I delete the normal one, but the other one still not create the needed pod.

What you expected to happen:
I hope the other one can quickly create the needed pod.

How to reproduce it (as minimally and precisely as possible):
My enviroment:
1 master + 1 node
two daemonsets have the same resource required: 700ms(cpu) + 700Mi(memory), but my node can only support one(e.g memory is not enough for 2 pods)

Anything else we need to know?: none

Environment:

• Kubernetes version (use kubectl version):
  build by myself:
  Client Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0-alpha.1.1355+6477f2b0fdbc0b", GitCommit:"6477f2b0fdbc0b7e72dccba5b5123e72244e9909", GitTreeState:"clean", BuildDate:"2018-01-25T03:06:42Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
  Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0-alpha.1.1355+6477f2b0fdbc0b", GitCommit:"6477f2b0fdbc0b7e72dccba5b5123e72244e9909", GitTreeState:"clean", BuildDate:"2018-01-25T02:48:14Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
• Cloud provider or hardware configuration: none
• OS (e.g. from /etc/os-release):CentOS Linux release 7.3.1611 (Core)
• Kernel (e.g. uname -a):Linux host-10-10-10-53 3.10.0-514.26.2.el7.x86_64 Unit test coverage in Kubelet is lousy. (~30%) #1 SMP Tue Jul 18 11:25:45 CST 2017 x86_64 x86_64 x86_64 GNU/Linux
• Install tools: ansible
• Others: none

[chentao1596]

/cc @k82cn
I found you have handle it when no-daemon pod deleted.
#46935
Please have a see, thank you!

[k82cn]

I delete the normal one, but the other one still not create the needed pod.

delete pod or DS?

[k82cn]

/sig apps

[chentao1596]

delete pod or DS?

delete DS.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close