Metadata timeout during cutover migration (OVN port unbound)

Description

During migratekit cutover (VMware → OpenStack), the migration succeeds at disk level, but the instance fails at boot time because cloud-init cannot reach OpenStack metadata service:

http://169.254.169.254/openstack/latest/meta_data.json: read: connection timed out

Steps to reproduce

• Run migratekit cutover
• VMware snapshot + disk copy completes successfully
• OpenStack volume attaches
• VM boots, but cloud-init fails

Actual result

• Metadata service is unreachable
• cloud-init fails
• Instance does not complete initialization

Observed issue

Neutron port is created but stays in:

binding_vif_type: unbound
status: DOWN

Example:

• Port exists
• IP assigned correctly
• But OVN binding is not completed at boot time

Expected result

• Port should be fully bound (ACTIVE) before VM boot
• Metadata route (169.254.169.254) should be reachable

Likely cause

Race condition: VM boots before OVN port binding + metadata proxy setup is complete.

Start by tracing the migratekit cutover path after the OpenStack volume attaches and the Neutron port is created. Inspect the ordering and wait logic around OVN binding and metadata proxy setup. Done means the port is bound before the VM boots and cloud-init can reach 169.254.169.254 during reproduction.