{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/contrib/issues/1960","repository_url":"https://api.github.com/repos/kubernetes/contrib","labels_url":"https://api.github.com/repos/kubernetes/contrib/issues/1960/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/contrib/issues/1960/comments","events_url":"https://api.github.com/repos/kubernetes/contrib/issues/1960/events","html_url":"https://github.com/kubernetes/contrib/issues/1960","id":186408474,"number":1960,"title":"[ansible] github-release option failing due to flannel timeouts","user":{"login":"wattsteve","id":3201484,"avatar_url":"https://avatars.githubusercontent.com/u/3201484?v=3","gravatar_id":"","url":"https://api.github.com/users/wattsteve","html_url":"https://github.com/wattsteve","followers_url":"https://api.github.com/users/wattsteve/followers","following_url":"https://api.github.com/users/wattsteve/following{/other_user}","gists_url":"https://api.github.com/users/wattsteve/gists{/gist_id}","starred_url":"https://api.github.com/users/wattsteve/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wattsteve/subscriptions","organizations_url":"https://api.github.com/users/wattsteve/orgs","repos_url":"https://api.github.com/users/wattsteve/repos","events_url":"https://api.github.com/users/wattsteve/events{/privacy}","received_events_url":"https://api.github.com/users/wattsteve/received_events","type":"User","site_admin":false},"labels":[{"id":344652606,"url":"https://api.github.com/repos/kubernetes/contrib/labels/area/ansible","name":"area/ansible","color":"009800","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-31T21:53:44Z","updated_at":"2016-11-16T23:50:30Z","closed_at":null,"body":"I have 4 nodes. 1 Master and 3 Workers. I am running Fedora 24 on all of them and have run dnf -y update on all of them as well. I ran the same experiment earlier today with the packageManager option and everything worked and I had a working Kube 1.2.2 cluster. However, I want a Kube 1.4 cluster, so I used the github-release option on an identical setup but new cluster and it fails with the exception below:\r\n\r\nTASK [flannel : Start flannel] *************************************************\r\nchanged: [leader.kube]\r\nfatal: [node-2.kube]: FAILED! => {\"changed\": false, \"failed\": true, \"msg\": \"Job for flanneld.service failed because a timeout was exceeded. See \\\"systemctl status flanneld.service\\\" and \\\"journalctl -xe\\\" for details.\\n\"}\r\nfatal: [node-1.kube]: FAILED! => {\"changed\": false, \"failed\": true, \"msg\": \"Job for flanneld.service failed because a timeout was exceeded. See \\\"systemctl status flanneld.service\\\" and \\\"journalctl -xe\\\" for details.\\n\"}\r\nfatal: [node-3.kube]: FAILED! => {\"changed\": false, \"failed\": true, \"msg\": \"Job for flanneld.service failed because a timeout was exceeded. See \\\"systemctl status flanneld.service\\\" and \\\"journalctl -xe\\\" for details.\\n\"}"},"comment":{"url":"https://api.github.com/repos/kubernetes/contrib/issues/comments/261110544","html_url":"https://github.com/kubernetes/contrib/issues/1960#issuecomment-261110544","issue_url":"https://api.github.com/repos/kubernetes/contrib/issues/1960","id":261110544,"user":{"login":"ingvagabund","id":8055242,"avatar_url":"https://avatars.githubusercontent.com/u/8055242?v=3","gravatar_id":"","url":"https://api.github.com/users/ingvagabund","html_url":"https://github.com/ingvagabund","followers_url":"https://api.github.com/users/ingvagabund/followers","following_url":"https://api.github.com/users/ingvagabund/following{/other_user}","gists_url":"https://api.github.com/users/ingvagabund/gists{/gist_id}","starred_url":"https://api.github.com/users/ingvagabund/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ingvagabund/subscriptions","organizations_url":"https://api.github.com/users/ingvagabund/orgs","repos_url":"https://api.github.com/users/ingvagabund/repos","events_url":"https://api.github.com/users/ingvagabund/events{/privacy}","received_events_url":"https://api.github.com/users/ingvagabund/received_events","type":"User","site_admin":false},"created_at":"2016-11-16T23:50:30Z","updated_at":"2016-11-16T23:50:30Z","body":"@wattsteve can you ssh to any of the machines, run ``systemctl start flannel`` manually and get output of ``systemctl status flannel`` (if there are some logs). Or run the flannel binary itself and get its error output?"}}
{"actor":{"display_login":"ingvagabund"}}