My env is one controller + two compute nodes. Here are the steps:

 

1. Create a VM at comp;
2. Live-migrate the VM from comp to comp2;
3. Live-migration success;
4. Live-migrate the VM from the comp2 to comp
5. Live migration fail

I find that there are duplicate records in the neutron's "ml2_port_bindings" table:

MariaDB [neutron]> select * from ml2_port_bindings where port_id="71c3a3c7-d853-4b26-9975-50b99c449371";
+--------------------------------------+-------+----------+-----------+---------------------------+---------------------------------------------------------------------------------------------------------------------------+----------+
| port_id | host | vif_type | vnic_type | profile | vif_details
                                 | status |
+--------------------------------------+-------+----------+-----------+---------------------------+---------------------------------------------------------------------------------------------------------------------------+----------+
| 71c3a3c7-d853-4b26-9975-50b99c449371 | comp | unbound | normal | {"migrating_to": "comp2"} |
                                 | INACTIVE |
| 71c3a3c7-d853-4b26-9975-50b99c449371 | comp2 | ovs | normal | {} | {"connectivity": "l2", "port_filter": true, "ovs_hybrid_plug": false, "datapath_type": "system", "bridge_name": "br-int"} | ACTIVE |
+--------------------------------------+-------+----------+-----------+---------------------------+---------------------------------------------------------------------------------------------------------------------------+----------+

 

Here is a duplicate record generated.

 

Why does nova or neutron generate an INACTIVE record in neutron's DB?

 

I have filed a bug at https://bugs.launchpad.net/nova/+bug/1900843.

 

Please feel free to give me some advice.

 

 

 

Thanks

Zhi Chang