yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1900843@xxxxxxxxxxxxxxxxxx>]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
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):
  Expired

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 with error "No valid host was found." 

  Detail error msg:
  2020-10-21 03:37:59.622 984895 ERROR nova.network.neutron [req-87a70f81-bdda-463d-8669-6a89fb33596e 0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 c89a4f7c36c248678addd9e07518cce3 - default default] [instance: 2aa8ff96-e04f-4897-af28-de4fb115ed65] Binding failed for port 71c3a3c7-d853-4b26-9975-50b99c449371 and host comp. Error: (409 {"NeutronError": {"type": "PortBindingAlreadyExists", "message": "Binding for port 71c3a3c7-d853-4b26-9975-50b99c449371 on host comp already exists.", "detail": ""}})

  
  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