Why do ebtables rules with share_dhcp_address block arp traffic?
We have openstack folsom installed on ubuntu in multi_host mode.
We decided to apply the shared_dhcp_address patch because we were using a lot of small tenants on a medium-ish cluster (50+ compute nodes).
However after application of the patch we found that the hypervisor is unable to ping a VM on another hypervisor. Before the patch this was working successfully.
The ebtables rules installed as part of the patch are blocking arp traffic made by the dnsmasq gateway IP.
What is the real reason behind putting those ebtables rules? What we have found that when we dropped the rules (manually), the communication seems to go through. So want to understand what is the purpose of those rules.
https://review.openstack.org/#/c/16578
[ Look at isolate_dhcp_address() in https://review.openstack.org/#/c/16578/6/nova/network/linux_net.py ]
I want to push this question as I have seen the same thing and blocking ARP means blocking DHCP, too. So why are these ebtables rules there?
The way to push the question is to vote it up, share it via social networks. This site is not a forum, there is no 'bumping'