yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1914747@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

It happens for me in ml2/ovs env for sure.

How to reproduce the issue:

1. Create trunk with some subport,
2. Spawn vm with plugged to the trunk's parent port,
3. Check status of trunk's parent port and subport's port - both are ACTIVE and have correct host_id,
4. Live-migrate vm
5. Check status of trunk's parent port and subport's port - subport is DOWN and has old host_id.

Due to that, if e.g. dvr and l2pop are used, connectivity to such subport is broken.
To fix it I needed to restart neutron-ovs-agent on the host to which vm was migrated to.

** Affects: neutron
     Importance: High
     Assignee: Slawek Kaplonski (slaweq)
         Status: Confirmed


** Tags: trunk

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1914747

Title:
  Trunk subport's port status and binding:host_id don't updated after
  live-migration

Status in neutron:
  Confirmed

Bug description:
  It happens for me in ml2/ovs env for sure.

  How to reproduce the issue:

  1. Create trunk with some subport,
  2. Spawn vm with plugged to the trunk's parent port,
  3. Check status of trunk's parent port and subport's port - both are ACTIVE and have correct host_id,
  4. Live-migrate vm
  5. Check status of trunk's parent port and subport's port - subport is DOWN and has old host_id.

  Due to that, if e.g. dvr and l2pop are used, connectivity to such subport is broken.
  To fix it I needed to restart neutron-ovs-agent on the host to which vm was migrated to.

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