Public bug reported:

Env: Ussuri environment with 1 controller + 2 compute nodes.

Reproduce 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   |
+--------------------------------------+-------+----------+-----------+---------------------------+---------------------------------------------------------------------------------------------------------------------------+----------+

After removing the "INACTIVE" record, I do the step4( live migrate the
VM from host2 to host1 ) success.

I find a similar bug at https://bugs.launchpad.net/nova/+bug/1822884.
But it seems that it is different from this bug.

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  Env: Ussuri environment with 1 controller + 2 compute nodes.
  
  Reproduce steps:
- 1. Create a VM at host1;
- 2. Live-migrate the VM from host1 to host2;
+ 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 host2 to host1;
+ 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   |
+                                  | status   |
  
+--------------------------------------+-------+----------+-----------+---------------------------+---------------------------------------------------------------------------------------------------------------------------+----------+
  | 71c3a3c7-d853-4b26-9975-50b99c449371 | comp  | unbound  | normal    | 
{"migrating_to": "comp2"} |
-                                  | INACTIVE |
+                                  | 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   |
  
+--------------------------------------+-------+----------+-----------+---------------------------+---------------------------------------------------------------------------------------------------------------------------+----------+
  
  After removing the "INACTIVE" record, I do the step4( live migrate the
  VM from host2 to host1 ) success.
  
- 
- I find a similar bug at https://bugs.launchpad.net/nova/+bug/1822884. But it 
seems that it is different with this bug.
+ I find a similar bug at https://bugs.launchpad.net/nova/+bug/1822884.
+ But it seems that it is different from this bug.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1900843

Title:
  Nova live-migration fails because duplicate records in neutron's
  ml2_port_bindings table

Status in OpenStack Compute (nova):
  New

Bug description:
  Env: Ussuri environment with 1 controller + 2 compute nodes.

  Reproduce 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   |
  
+--------------------------------------+-------+----------+-----------+---------------------------+---------------------------------------------------------------------------------------------------------------------------+----------+

  After removing the "INACTIVE" record, I do the step4( live migrate the
  VM from host2 to host1 ) success.

  I find a similar bug at https://bugs.launchpad.net/nova/+bug/1822884.
  But it seems that it is different from this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1900843/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to