{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61256","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61256/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61256/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61256/events","html_url":"https://github.com/kubernetes/kubernetes/issues/61256","id":305787308,"number":61256,"title":"Pod become unshedulable after our 'upgrade' operation","user":{"login":"xrmzju","id":27884109,"avatar_url":"https://avatars3.githubusercontent.com/u/27884109?v=4","gravatar_id":"","url":"https://api.github.com/users/xrmzju","html_url":"https://github.com/xrmzju","followers_url":"https://api.github.com/users/xrmzju/followers","following_url":"https://api.github.com/users/xrmzju/following{/other_user}","gists_url":"https://api.github.com/users/xrmzju/gists{/gist_id}","starred_url":"https://api.github.com/users/xrmzju/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xrmzju/subscriptions","organizations_url":"https://api.github.com/users/xrmzju/orgs","repos_url":"https://api.github.com/users/xrmzju/repos","events_url":"https://api.github.com/users/xrmzju/events{/privacy}","received_events_url":"https://api.github.com/users/xrmzju/received_events","type":"User","site_admin":false},"labels":[{"id":617149945,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/needs-sig","name":"needs-sig","color":"ededed","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-03-16T03:04:22Z","updated_at":"2018-04-02T13:56:24Z","closed_at":null,"author_association":"NONE","body":"<!-- This form is for bug reports and feature requests ONLY! \r\n\r\nIf you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).\r\n-->\r\n\r\n**Is this a BUG REPORT or FEATURE REQUEST?**:\r\n\r\n> Uncomment only one, leave it on its own line: \r\n>\r\n> /kind bug\r\n\r\n**What happened**:\r\npod become Unschedulable  and never come up or raise a new one only if we kill the `Unschedulable`  pod\r\n[root@master1 ~]# kubectl get po\r\nNAME                                  READY     STATUS          RESTARTS   AGE\r\ngo-653831134-3q13m              0/1       Unschedulable   0          1d\r\n**What you expected to happen**:\r\na new pod come up or the pod do not become unshedulable.\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\n1.  create a pod\r\n2. set the node where the pod schedulered to  `Unschedulable`\r\n3. restart the kubelet\r\n4. set the node where the pod schedulered to  schedulable again. the pod \r\n\r\n**Anything else we need to know?**:\r\nin our environment, we want to do kubelet upgrade(means `replace and restart the kubelet`) without pod eviction, so we set the controller-manager eviction-timeout a little bit longer than replacement time. and we don't want new pod to be scheduled to the `upgrading` status node, so we set the node Unschedulable during the kubelet replacement and recover it after the replacement.  then it comes up the old pod was rejected by the kubelet because the node was unshedulable at that time. so i wonder if  kubelet can find out a way to know whether the pod is a new scheduled one or a existed one,  and treated it in a different way. is it resonable?\r\n**Environment**:\r\n- Kubernetes version (use `kubectl version`): 1.7.4\r\n- Cloud provider or hardware configuration:\r\n- OS (e.g. from /etc/os-release): centos\r\n- Kernel (e.g. `uname -a`):\r\n- Install tools:\r\n- Others:\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/377934434","html_url":"https://github.com/kubernetes/kubernetes/issues/61256#issuecomment-377934434","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61256","id":377934434,"user":{"login":"dims","id":23304,"avatar_url":"https://avatars2.githubusercontent.com/u/23304?v=4","gravatar_id":"","url":"https://api.github.com/users/dims","html_url":"https://github.com/dims","followers_url":"https://api.github.com/users/dims/followers","following_url":"https://api.github.com/users/dims/following{/other_user}","gists_url":"https://api.github.com/users/dims/gists{/gist_id}","starred_url":"https://api.github.com/users/dims/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dims/subscriptions","organizations_url":"https://api.github.com/users/dims/orgs","repos_url":"https://api.github.com/users/dims/repos","events_url":"https://api.github.com/users/dims/events{/privacy}","received_events_url":"https://api.github.com/users/dims/received_events","type":"User","site_admin":false},"created_at":"2018-04-02T13:56:24Z","updated_at":"2018-04-02T13:56:24Z","author_association":"MEMBER","body":"/sig node"}}
{"actor":{"display_login":"dims"}}