masquerade binding: connectivity lost after VM migration

[maiqueb]

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
After a VM is migrated, it loses connectivity from the outside world on its masquerade interface.

We should make sure that the connectivity becomes available immediately after the migration.

What you expected to happen:
Connectivity should be preserved.

How to reproduce it (as minimally and precisely as possible):

1. Create VM with masquerade binding; start an http / TCP server on it.
2. Continuously access the VM's service
3. Migrate VM with masquerade binding.
4. Connectivity is lost after migration.

Anything else we need to know?:
Connectivity will recover after the mac address update of the in-pod bridge is propagated via ARP.

Environment:

• KubeVirt version (use virtctl version):
• Kubernetes version (use kubectl version):
• VM or VMI specifications:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[maiqueb]

/remove-lifecycle stale