I have found the cause of both the issues Issue 1: external_network_bridge is by default set to br-ex therefore demanding that external_network_gateway and router_id be set for everything to work. In order to achieve the legacy mode where the l3-agent can handle multiple external networks and gateways we have to explicitly set 'external_network_bridge' to null like below
external_network_bridge = Issue 2: Since I had two external network I was running two l3-agents and somehow the second l3-agent was picking up the floating ip messages from the queue server before the first one could and this was preventing from floatingip to be updated without a restart. As soon as I stopped the second l3 agent things were back to normal. Hope the information is useful to everyone. Thank you, Ageeleshwar K On Wed, Feb 11, 2015 at 6:42 PM, Akilesh K <akilesh1...@gmail.com> wrote: > Hi, > I have some issues with l3-agent, explained below. Kindly let me know how > to debug the same and conclude if its a bug or misconfiguration. > > Issue 1: > 1. The router namespace is not created unless I set router_id, > external_network_gateway, and external_network_bridge in l3-agent.ini. As > per the documentation these need not be set unless I want to lock down my > l3-agent to one router or external network. > > Issue 2: > Each time I associate a floatingip I have to restart my l3-agent in order > for it to take effect. Only after restart the relevant iptable rules are > populated. > > Let me know how can I proceed. > > Thank you, > Ageeleshwar K >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
