Swaminathan Vasudevan (swaminathan-vasudevan) gave a good analysis at https://bugs.launchpad.net/neutron/+bug/1358718. So I think this is not a bug.
** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1411874 Title: DVR router is seen on multiple controller nodes Status in OpenStack Neutron (virtual network service): Invalid Bug description: I have Openstack deployed with DVR support. I did following to setup my networks neutron net-create demo-net netdemoaid=$(neutron net-list | awk '{if($4=="'demo-net'"){print $2;}}') neutron subnet-create demo-net 10.100.102.0/24 --name demo-subnet subnetdemoid=$(neutron subnet-list | awk '{if($4=="'demo-subnet'"){print $2;}}') neutron router-create demo-router routerdemoid=$(neutron router-list | awk '{if($4=="'demo-router'"){print $2;}}') exnetid=$(neutron net-list | awk '{if($4=="'ext-net'"){print $2;}}') neutron router-gateway-set $routerdemoid $exnetid neutron router-interface-add demo-router $subnetdemoid root@Linux:/tmp# neutron l3-agent-list-hosting-router 9182ecba-00ac-42ce-b0d1-801003bb1b14 +--------------------------------------+--------------------------------------------------+----------------+-------+ | id | host | admin_state_up | alive | +--------------------------------------+--------------------------------------------------+----------------+-------+ | 2d6505ef-e7a5-4672-a040-3a50f764a193 | controller-controller1-25ic4624koca | True | :-) | +--------------------------------------+--------------------------------------------------+----------------+-------+ Then I boot an instance: nova boot --image cirros --flavor m1.tiny --key-name default --nic net-id=$netdemoid cirrosinstance root@Linux:/tmp# neutron l3-agent-list-hosting-router 9182ecba-00ac-42ce-b0d1-801003bb1b14 +--------------------------------------+-----------------------------------------------------+----------------+-------+ | id | host | admin_state_up | alive | +--------------------------------------+-----------------------------------------------------+----------------+-------+ | 2d6505ef-e7a5-4672-a040-3a50f764a193 | controller-controller1-25ic4624koca | True | :-) | | 339eb96b-9c9d-400a-a45f-e0f2ed6ebf2e | controller-controller0-tqqqqwwogbnv | True | :-) | | 6b1cc42d-f701-47ba-a0fc-661fb3bc22ae | novacompute2-novacompute2-b4jb7jtppnas | True | :-) | | fdffb433-b5f6-4d10-bdc4-2030a9800b2a | controller-controller2-7piq4lqrgtma | True | :-) | +--------------------------------------+-----------------------------------------------------+----------------+-------+ We have qrouter binded to three controllers instead of just one controller. We have qrouter binded to novacompute2 because we have DVR enabled, and instance is on this compute node. Look at "ip netns", only have SNAT on controller1 DHCP servers for subnetdemo are running on controller0 and controller2 We only need qrouter bind to one controller, not three controllers. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1411874/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp