Swami I don't think it's a duplicate. I can reproduce it all the time when using Liberty.
I don't think the GARP from the new node is to blame.
I get ARP replies for the same floating ip from both nodes (the new one and the old one) even a long time after the migration.
Cleaning the route in the fip namespace of the old host:
10.127.128.12 via 169.254.31.28 dev fpr-7d1a001a-9
that is the route for the fip of the vm that migrated solves the issue.
NOTE: pinging the fip from the nodes of the cloud works all the time. To reproduce you need to ping from an external host.
Swami I don't think it's a duplicate. I can reproduce it all the time when using Liberty.
I don't think the GARP from the new node is to blame.
I get ARP replies for the same floating ip from both nodes (the new one and the old one) even a long time after the migration.
Cleaning the route in the fip namespace of the old host:
10.127.128.12 via 169.254.31.28 dev fpr-7d1a001a-9
that is the route for the fip of the vm that migrated solves the issue.
NOTE: pinging the fip from the nodes of the cloud works all the time. To reproduce you need to ping from an external host.