Public bug reported: I have a mitaka enviroment with one controller host, one network host and two computer hosts. All the l3 agents of my computer hosts and network host are configed as dvr_snat mode. I created a dvr+ha router and boot a vm with one of subnet associated with this router. This vm accesses the internet normally before or after associating a floating ip with it. But when I disassociated the floating ip, the vm can not access the internet any more.
Pre-conditions: run L3 agent with dvr_snat mode on network nodes and compute nodes How to reprocude: create a dvr+ha router create a subnet and associate this subnet with the router create a vm with the subnet associate a floating ip with the vm and then disassociate it the vm can not access internet Analysis: I found that the ip rule "36709: from 10.10.30.4 lookup 16"(this ip is the vm's fixed ip) is still in the router's qrouter namespace on the compute host, although I diassociated the floating ip. Then I debug the code and found dvr_edge_ha_router can not execute code into remove_floating_ip function. ** Affects: neutron Importance: Undecided Assignee: Zhixin Li (lizhixin) Status: New ** Tags: l3-dvr-backlog l3-ha ** Changed in: neutron Assignee: (unassigned) => Zhixin Li (lizhixin) ** Description changed: I have a mitaka enviroment with one controller host, one network host and two computer hosts. All the l3 agents of my computer hosts and network host are configed as dvr_snat mode. I created a dvr+ha router and boot a vm with one of subnet associated with this router. This vm accesses the internet normally before or after associating a floating ip with it. But when I disassociated the floating ip, the vm can not access the internet any more. - Pre-conditions: - run L3 agent with dvr_snat mode on network nodes and compute nodes + run L3 agent with dvr_snat mode on network nodes and compute nodes How to reprocude: - create a dvr+ha router - create a subnet and associate this subnet with the router - create a vm with the subnet - associate a floating ip with the vm and then disassociate it - the vm can not access internet + create a dvr+ha router + create a subnet and associate this subnet with the router + create a vm with the subnet + associate a floating ip with the vm and then disassociate it + the vm can not access internet Analysis: - I found that the ip rule "36709: from 10.10.30.4 lookup 16"(this ip is the vm's fixed ip) is still in the router's qrouter namespace on the compute host, although I diassociated the floating ip. Then I debug the code and found dvr_edge_ha_router can not execute code into remove_floating_ip function. + I found that the ip rule "36709: from 10.10.30.4 lookup 16"(this ip is the vm's fixed ip) is still in the router's qrouter namespace on the compute host, although I diassociated the floating ip. Then I debug the code and found dvr_edge_ha_router can not execute code into remove_floating_ip function. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1644415 Title: dvr_edge_ha_router disassociates floatingip incompletely Status in neutron: New Bug description: I have a mitaka enviroment with one controller host, one network host and two computer hosts. All the l3 agents of my computer hosts and network host are configed as dvr_snat mode. I created a dvr+ha router and boot a vm with one of subnet associated with this router. This vm accesses the internet normally before or after associating a floating ip with it. But when I disassociated the floating ip, the vm can not access the internet any more. Pre-conditions: run L3 agent with dvr_snat mode on network nodes and compute nodes How to reprocude: create a dvr+ha router create a subnet and associate this subnet with the router create a vm with the subnet associate a floating ip with the vm and then disassociate it the vm can not access internet Analysis: I found that the ip rule "36709: from 10.10.30.4 lookup 16"(this ip is the vm's fixed ip) is still in the router's qrouter namespace on the compute host, although I diassociated the floating ip. Then I debug the code and found dvr_edge_ha_router can not execute code into remove_floating_ip function. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1644415/+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