{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/63475","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/63475/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/63475/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/63475/events","html_url":"https://github.com/kubernetes/kubernetes/issues/63475","id":320680288,"node_id":"MDU6SXNzdWUzMjA2ODAyODg=","number":63475,"title":"iscsi PV does not recover under a node down.","user":{"login":"dElogics","id":8318735,"node_id":"MDQ6VXNlcjgzMTg3MzU=","avatar_url":"https://avatars3.githubusercontent.com/u/8318735?v=4","gravatar_id":"","url":"https://api.github.com/users/dElogics","html_url":"https://github.com/dElogics","followers_url":"https://api.github.com/users/dElogics/followers","following_url":"https://api.github.com/users/dElogics/following{/other_user}","gists_url":"https://api.github.com/users/dElogics/gists{/gist_id}","starred_url":"https://api.github.com/users/dElogics/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dElogics/subscriptions","organizations_url":"https://api.github.com/users/dElogics/orgs","repos_url":"https://api.github.com/users/dElogics/repos","events_url":"https://api.github.com/users/dElogics/events{/privacy}","received_events_url":"https://api.github.com/users/dElogics/received_events","type":"User","site_admin":false},"labels":[{"id":105146071,"node_id":"MDU6TGFiZWwxMDUxNDYwNzE=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/kind/bug","name":"kind/bug","color":"e11d21","default":false},{"id":169428334,"node_id":"MDU6TGFiZWwxNjk0MjgzMzQ=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/storage","name":"sig/storage","color":"d2b48c","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-05-07T05:43:16Z","updated_at":"2018-10-02T17:51:44Z","closed_at":null,"author_association":"NONE","body":"/kind bug\r\n**What happened**:\r\nSuppose a pod is bound to a PV and the node running that pod goes down. Under default configuration, the PV must be force-detached from the node which got down within 6 minutes (I think depending on --attach-detach-reconcile-sync-period) and successfully relocate to another node; however in the other node, the pod is stuck at ContainerCreating state unless the \r\n1) Node is deleted\r\n2) Controller is restarted.\r\n\r\nLooking at the bug reports #57497, #50004, #50200, this bug appears to be fixed in many PV drivers, but not in the iscsi one.\r\n\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\nMake a node unavailable by taking it's IP out, or pkill kubelet, or crash kernel, poweroff hardware/VM etc...\r\n\r\n**Environment**:\r\n- Kubernetes version (use `kubectl version`): \r\nClient Version: version.Info{Major:\"1\", Minor:\"8\", GitVersion:\"v1.8.2\", GitCommit:\"bdaeafa71f6c7c04636251031f93464384d54963\", GitTreeState:\"clean\", BuildDate:\"2017-10-24T19:48:57Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\nServer Version: version.Info{Major:\"1\", Minor:\"8\", GitVersion:\"v1.8.2\", GitCommit:\"bdaeafa71f6c7c04636251031f93464384d54963\", GitTreeState:\"clean\", BuildDate:\"2017-10-24T19:38:10Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n- Cloud provider or hardware configuration:\r\nBare metal, 512GB, 4 proc nodes.\r\n- OS (e.g. from /etc/os-release):\r\nPRETTY_NAME=\"Debian GNU/Linux 9 (stretch)\"\r\nNAME=\"Debian GNU/Linux\"\r\nVERSION_ID=\"9\"\r\nVERSION=\"9 (stretch)\"\r\nID=debian\r\nHOME_URL=\"https://www.debian.org/\"\r\nSUPPORT_URL=\"https://www.debian.org/support\"\r\nBUG_REPORT_URL=\"https://bugs.debian.org/\"\r\n- Kernel (e.g. `uname -a`):\r\nLinux aws-prod132 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux\r\n- Install tools:\r\n- Others:\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/426368968","html_url":"https://github.com/kubernetes/kubernetes/issues/63475#issuecomment-426368968","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/63475","id":426368968,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNjM2ODk2OA==","user":{"login":"adampl","id":6024937,"node_id":"MDQ6VXNlcjYwMjQ5Mzc=","avatar_url":"https://avatars1.githubusercontent.com/u/6024937?v=4","gravatar_id":"","url":"https://api.github.com/users/adampl","html_url":"https://github.com/adampl","followers_url":"https://api.github.com/users/adampl/followers","following_url":"https://api.github.com/users/adampl/following{/other_user}","gists_url":"https://api.github.com/users/adampl/gists{/gist_id}","starred_url":"https://api.github.com/users/adampl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adampl/subscriptions","organizations_url":"https://api.github.com/users/adampl/orgs","repos_url":"https://api.github.com/users/adampl/repos","events_url":"https://api.github.com/users/adampl/events{/privacy}","received_events_url":"https://api.github.com/users/adampl/received_events","type":"User","site_admin":false},"created_at":"2018-10-02T17:51:44Z","updated_at":"2018-10-02T17:51:44Z","author_association":"NONE","body":"I don't remember now, but probably AWS and/or GCE. Now I'm not even sure if it's actually fixed, or it's just a difference in behavior. Some providers actually remove the node from the cluster when it's shut down, which AFAIK somehow helps K8S to force-detach the volume. But generally, several solutions for this problem appeared over time as pull requests (like #67977), but eventually they have been held/canceled in favor of something better (like #65392)."}}
{"actor":{"display_login":"adampl"}}