{"action":"created","issue":{"url":"https://api.github.com/repos/google/metallb/issues/330","repository_url":"https://api.github.com/repos/google/metallb","labels_url":"https://api.github.com/repos/google/metallb/issues/330/labels{/name}","comments_url":"https://api.github.com/repos/google/metallb/issues/330/comments","events_url":"https://api.github.com/repos/google/metallb/issues/330/events","html_url":"https://github.com/google/metallb/issues/330","id":371039442,"node_id":"MDU6SXNzdWUzNzEwMzk0NDI=","number":330,"title":"Metallb doesn't send/receive ARP when Istio is enabled","user":{"login":"vijaykumark","id":13167000,"node_id":"MDQ6VXNlcjEzMTY3MDAw","avatar_url":"https://avatars3.githubusercontent.com/u/13167000?v=4","gravatar_id":"","url":"https://api.github.com/users/vijaykumark","html_url":"https://github.com/vijaykumark","followers_url":"https://api.github.com/users/vijaykumark/followers","following_url":"https://api.github.com/users/vijaykumark/following{/other_user}","gists_url":"https://api.github.com/users/vijaykumark/gists{/gist_id}","starred_url":"https://api.github.com/users/vijaykumark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vijaykumark/subscriptions","organizations_url":"https://api.github.com/users/vijaykumark/orgs","repos_url":"https://api.github.com/users/vijaykumark/repos","events_url":"https://api.github.com/users/vijaykumark/events{/privacy}","received_events_url":"https://api.github.com/users/vijaykumark/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-17T12:06:13Z","updated_at":"2018-10-17T12:07:40Z","closed_at":null,"author_association":"NONE","body":"**Is this a bug report or a feature request?**:\r\n\r\nBug. Metallb doesn't send or receive ARP requests when Istio is enabled.\r\n\r\n**What happened**:\r\nInstalled Istio 1.0.2 on Kubernetes v1.11.2, CoreOS. After that installed metallb v0.7.3 and added configuration.\r\nAdd loadbalancer ip to a service and it shows that the service got the loadbalancer IP.\r\n\r\nThere are no logs which say \"got ARP request for service IP\" as shown below:\r\n```\r\nspeaker-5w68n speaker {\"caller\":\"arp.go:102\",\"interface\":\"eno50\",\"ip\":\"10.10.2.47\",\"msg\":\"got ARP request for service IP, sending response\",\"responseMAC\":\"52:73:33:a6:be:1a\",\"senderIP\":\"10.10.2.47\",\"senderMAC\":\"52:73:33:a6:be:1a\",\"ts\":\"2018-10-17T11:49:26.332788288Z\"}\r\n```\r\n\r\n**What you expected to happen**:\r\n\r\nMetallb should send and receive ARP requests and loadbalancerIP is working fine. Istio should not cause any problems to metallb.\r\n\r\n\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\nInstall k8s v1.11.2 and install Istio v1.0.2 on CoreOS \r\n\r\n\r\n**Anything else we need to know?**:\r\n\r\nWe are running kubernetes on CoreOS on bare metal cluster.\r\n\r\n**Environment**:\r\n- MetalLB version: v0.73\r\n- Kubernetes version: v1.11.2\r\n- BGP router type/version: layer2\r\n- OS (e.g. from /etc/os-release):\r\nNAME=\"Container Linux by CoreOS\"\r\nID=coreos\r\nVERSION=1855.4.0\r\nVERSION_ID=1855.4.0\r\nBUILD_ID=2018-09-11-0003\r\nPRETTY_NAME=\"Container Linux by CoreOS 1855.4.0 (Rhyolite)\"\r\nANSI_COLOR=\"38;5;75\"\r\nHOME_URL=\"https://coreos.com/\"\r\nBUG_REPORT_URL=\"https://issues.coreos.com\"\r\nCOREOS_BOARD=\"amd64-usr\"\r\n\r\n- Kernel (e.g. `uname -a`):\r\nLinux system 4.14.67-coreos #1 SMP Mon Sep 10 23:14:26 UTC 2018 x86_64 Intel(R) Xeon(R) CPU E5-2665 0 @ 2.40GHz GenuineIntel GNU/Linux\r\n"},"comment":{"url":"https://api.github.com/repos/google/metallb/issues/comments/430602267","html_url":"https://github.com/google/metallb/issues/330#issuecomment-430602267","issue_url":"https://api.github.com/repos/google/metallb/issues/330","id":430602267,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMDYwMjI2Nw==","user":{"login":"vijaykumark","id":13167000,"node_id":"MDQ6VXNlcjEzMTY3MDAw","avatar_url":"https://avatars3.githubusercontent.com/u/13167000?v=4","gravatar_id":"","url":"https://api.github.com/users/vijaykumark","html_url":"https://github.com/vijaykumark","followers_url":"https://api.github.com/users/vijaykumark/followers","following_url":"https://api.github.com/users/vijaykumark/following{/other_user}","gists_url":"https://api.github.com/users/vijaykumark/gists{/gist_id}","starred_url":"https://api.github.com/users/vijaykumark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vijaykumark/subscriptions","organizations_url":"https://api.github.com/users/vijaykumark/orgs","repos_url":"https://api.github.com/users/vijaykumark/repos","events_url":"https://api.github.com/users/vijaykumark/events{/privacy}","received_events_url":"https://api.github.com/users/vijaykumark/received_events","type":"User","site_admin":false},"created_at":"2018-10-17T12:07:40Z","updated_at":"2018-10-17T12:07:40Z","author_association":"NONE","body":"@danderson  Any clue how to fix this issue? \r\nI have another cluster without Istio in the same network environment and metallb is working fine there.\r\nHow to troubleshoot metallb + istio issue? Checked kube-proxy and we have not configured IPVS."}}
{"actor":{"display_login":"vijaykumark"}}