no rule added after updating floatingip

[abel]

At first, there are 5 vms with floatingips on the same one host and in the same subnet.
+------+-----------+---------------+
| id | fixed ip | floatingip |
+------+-----------+---------------+
| vm1 | 10.0.0.4 | 10.187.165.52 |
| vm2 | 10.0.0.5 | 10.187.165.53 |
| vm3 | 10.0.0.6 | 10.187.165.54 |
| vm4 | 10.0.0.7 | 10.187.165.55 |
| vm5 | 10.0.0.8 | 10.187.165.56 |
| vm6 | 10.0.0.9 | |
| vm7 | 10.0.0.10 | |
| vm8 | 10.0.0.11 | |
| vm9 | 10.0.0.12 | |
| vm10 | 10.0.0.13 | |
+------+-----------+---------------+

then, dissassociate the floatingip and associate to vm6~vm10.
in the loop:
 floatingip-disassociate FIP-ID
 floatingip-associate FIP-ID PORT-ID

we found no rule added in the ns qrouter-*, there is the old rules
on the compute node:
$ ip net exec qrouter-72da0968-f904-4bce-a1d5-bf3f00f7fb6e ip rule list
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
52104: from 10.0.0.4 lookup 16
52108: from 10.0.0.5 lookup 16
52109: from 10.0.0.6 lookup 16
60018: from 10.0.0.7 lookup 16
60019: from 10.0.0.8 lookup 16
69642: from 10.0.0.9 lookup 16
167772161: from 10.0.0.1/24 lookup 167772161

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Bug closed due to lack of activity, please feel free to reopen if needed.