{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61170","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61170/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61170/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61170/events","html_url":"https://github.com/kubernetes/kubernetes/issues/61170","id":305097644,"node_id":"MDU6SXNzdWUzMDUwOTc2NDQ=","number":61170,"title":"Kubernetes fails obscurely with two network interfaces","user":{"login":"egrimley","id":12933337,"node_id":"MDQ6VXNlcjEyOTMzMzM3","avatar_url":"https://avatars1.githubusercontent.com/u/12933337?v=4","gravatar_id":"","url":"https://api.github.com/users/egrimley","html_url":"https://github.com/egrimley","followers_url":"https://api.github.com/users/egrimley/followers","following_url":"https://api.github.com/users/egrimley/following{/other_user}","gists_url":"https://api.github.com/users/egrimley/gists{/gist_id}","starred_url":"https://api.github.com/users/egrimley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/egrimley/subscriptions","organizations_url":"https://api.github.com/users/egrimley/orgs","repos_url":"https://api.github.com/users/egrimley/repos","events_url":"https://api.github.com/users/egrimley/events{/privacy}","received_events_url":"https://api.github.com/users/egrimley/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":173493665,"node_id":"MDU6TGFiZWwxNzM0OTM2NjU=","url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/node","name":"sig/node","color":"d2b48c","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-03-14T10:18:29Z","updated_at":"2018-09-02T11:07:47Z","closed_at":null,"author_association":"NONE","body":"/kind bug\r\n/sig Node bugs\r\n\r\nI would probably have reopened #44702 if that were an option.\r\n\r\nIf I create a two-node cluster in which each node has two network interfaces and the nodes communicate via their second network interface then everything seems to work until I try `kubectl logs`. Eventually I realised that `kubectl get pods --all-namespaces -o wide` is showing the wrong IP addresses, as described under #44702, though in my case both nodes are getting the wrong IP address.\r\n\r\nThere is a work-around, but it's tedious. On Ubuntu, on each node:\r\n\r\n* Edit `/etc/systemd/system/kubelet.service.d/10-kubeadm.conf` and add the line `KUBELET_EXTRA_ARGS=--node-ip=...` replacing `...` with the IP address that should be used for connecting to that node from another node.\r\n\r\n* `systemctl daemon-reload`\r\n\r\n* `systemctl restart kubelet`\r\n\r\nI told the master which IP address it should use by running`\"kubeadm init --apiserver-advertise-address=...`. That information should be propagated to `kubelet`.\r\n\r\nThe worker should presumably take its IP address from the connection it opened to the master. (I cannot think of a good reason why it would need its IP address before it connects. If for some not-so-good reason it does then perhaps an additional command-line argument to `kubeadm join` would be required to let the user override the silly take-the-first-non-loopback-interface heuristic.)\r\n\r\nIf for some reason it is really not possible to make Kubernetes work correctly unless communication between nodes always goes via the first non-loopback interface (a somewhat embarrassing limitation to have to document) then there should at least be a clear error message when this condition is not satisfied rather than an obscure failure when certain features are used for the first time.\r\n\r\nI have been testing versions 1.9.1, 1.9.2 and 1.9.3 with several different network configurations."},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/417922349","html_url":"https://github.com/kubernetes/kubernetes/issues/61170#issuecomment-417922349","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/61170","id":417922349,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNzkyMjM0OQ==","user":{"login":"fejta-bot","id":30488982,"node_id":"MDQ6VXNlcjMwNDg4OTgy","avatar_url":"https://avatars1.githubusercontent.com/u/30488982?v=4","gravatar_id":"","url":"https://api.github.com/users/fejta-bot","html_url":"https://github.com/fejta-bot","followers_url":"https://api.github.com/users/fejta-bot/followers","following_url":"https://api.github.com/users/fejta-bot/following{/other_user}","gists_url":"https://api.github.com/users/fejta-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/fejta-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fejta-bot/subscriptions","organizations_url":"https://api.github.com/users/fejta-bot/orgs","repos_url":"https://api.github.com/users/fejta-bot/repos","events_url":"https://api.github.com/users/fejta-bot/events{/privacy}","received_events_url":"https://api.github.com/users/fejta-bot/received_events","type":"User","site_admin":false},"created_at":"2018-09-02T11:07:47Z","updated_at":"2018-09-02T11:07:47Z","author_association":"NONE","body":"Issues go stale after 90d of inactivity.\nMark the issue as fresh with `/remove-lifecycle stale`.\nStale issues rot after an additional 30d of inactivity and eventually close.\n\nIf this issue is safe to close now please do so with `/close`.\n\nSend feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).\n/lifecycle stale"}}
{"actor":{"display_login":"fejta-bot"}}