Public bug reported: ENV: master devstack multinode install: 1 controller node 2 compute nodes -> dvr_no_external (compute1, compute2) 2 network nodes -> dvr_snat (network1, network2)
Problem: For L3 DVR HA router, when the network node, which hosting the `master` router, is down and up. The router port `device_owner = network:router_gateway` will be binding back to the `down` host. How to reproduce: 1. create DVR_HA router connecting user private network and public external network 2. create a VM in dvr_no_external compute in private network 3. create floating IP and associate to the VM port 4. directly reboot the `master` router located host (network1) Some testing output: (1) before reboot: router `master` is stay in network1 http://paste.openstack.org/show/730423/ (2) during reboot: http://paste.openstack.org/show/730424/ (3) after reboot: router `master` is in network2 http://paste.openstack.org/show/730422/ network:router_gateway port is binding back to network1. network:router_centralized_snat is normally binding to network2. ** Affects: neutron Importance: Undecided Status: New ** Description changed: ENV: master devstack multinode install: 1 controller node 2 compute nodes -> dvr_no_external (compute1, compute2) 2 network nodes -> dvr_snat (network1, network2) - Problem: For L3 DVR HA router, when the network node, which hosting the `master` router, is down and up. - The router port `device_owner = network:router_gateway` will go back to the `down` host. - - How to reproduce: - 1. create DVR_HA router connecting user private network and public external network - 2. create a VM in dvr_no_external compute in private network + The router port `device_owner = network:router_gateway` will be binding back to the `down` host. How to reproduce: 1. create DVR_HA router connecting user private network and public external network 2. create a VM in dvr_no_external compute in private network 3. create floating IP and associate to the VM port - 4. directly reboot the `master` router located host - + 4. directly reboot the `master` router located host (network1) Some testing output: (1) before reboot: router `master` is stay in network1 http://paste.openstack.org/show/730423/ (2) during reboot: http://paste.openstack.org/show/730424/ (3) after reboot: router `master` is in network2 http://paste.openstack.org/show/730422/ network:router_gateway port is binding back to network1. network:router_centralized_snat is normally binding to network2. ** Summary changed: - [dvr_no_external][ha] router_gateway port binding host goes wrong after the HA state change + [dvr][ha] router_gateway port binding host goes wrong after the HA state change ** Summary changed: - [dvr][ha] router_gateway port binding host goes wrong after the HA state change + [dvr][ha] router_gateway port binding host goes wrong after the 'master' host down/up -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1793529 Title: [dvr][ha] router_gateway port binding host goes wrong after the 'master' host down/up Status in neutron: New Bug description: ENV: master devstack multinode install: 1 controller node 2 compute nodes -> dvr_no_external (compute1, compute2) 2 network nodes -> dvr_snat (network1, network2) Problem: For L3 DVR HA router, when the network node, which hosting the `master` router, is down and up. The router port `device_owner = network:router_gateway` will be binding back to the `down` host. How to reproduce: 1. create DVR_HA router connecting user private network and public external network 2. create a VM in dvr_no_external compute in private network 3. create floating IP and associate to the VM port 4. directly reboot the `master` router located host (network1) Some testing output: (1) before reboot: router `master` is stay in network1 http://paste.openstack.org/show/730423/ (2) during reboot: http://paste.openstack.org/show/730424/ (3) after reboot: router `master` is in network2 http://paste.openstack.org/show/730422/ network:router_gateway port is binding back to network1. network:router_centralized_snat is normally binding to network2. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1793529/+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