It is the VM operating systems responsibility to send out a GARP when the IP address is added.
This issue will not occur if the same IP address has not been used recently with a different MAC address.
It is always a good practice to send out GARP when IP address is added.
Workaround:
From the impacted VM, that is the redeployed VM, you can manually run an '
arping' command to update all devices of the new IP/MAC mapping:
arping -U -I eth0 172.16.20.10 -c 3
The IP address in the command should be the IP address of the redeployed VM and will result in a GARP being sent out with source and destination IP being the same and that of the newly deployed VM.