Comment 5 for bug 1414779

ZongKa LI,

 The issue here is that the rule priority associated to a floatingip is not saved over agent restart. The fix I am providing preserves such associations over agent restart so that future allocations of rule priorities do not collide with previous allocations.

 1. Spawn a VM and associate a floatingip1
2. Restart the Agent
3. Spawn a second VM with floatingip2

if both the floatingips are on the same external network, without the fix there will be duplicate ip rule priorities would be the same for both the floating ips, with the fix they won't

I had one router, I created one VM , associated a floating ip to the VM. Thereafter restarted the agent. Created another VM and associated a floating ip. This is what appears:

sdn@rg-oscv-cn2:~/devstack$ sudo ip netns exec qrouter-b5fb2ae4-ae83-4b46-b0b2-9960c853e61f ip rule s
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
32768: from 152.2.0.10 lookup 16
32768: from 152.2.0.21 lookup 16
2550267905: from 152.2.0.1/16 lookup 2550267905

After the fix that has been submitted for this bug report:

sdn@rg-oscv-cn2:~/devstack$ sudo ip netns exec qrouter-006f497f-86db-4685-b305-c0dcb203dd00 ip rule s
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
65937: from 152.2.0.10 lookup 16
71986: from 152.2.0.21 lookup 16