yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1541738@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

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

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

Title:
  Rule on the tun bridge is not updated in time while migrating the vm

Status in neutron:
  Expired

Bug description:
  ENV：neutron/master, vxlan

  After the vm live migration, we can observe that the vm is active
  using command "nova show". However, the vm network is not ready. When
  processing vm live migration, nova invokes neutron update_port. It
  only updates the host ID of the port attribute, but doesn't update the
  rules on the tun bridge. This means the output port in the rule below
  is not updated to the vxlan port, which should be connected to the
  host node that the vm is migrated to.

  ovs-ofctl dump-flows br-tun | grep 1ef
  cookie=0x0, duration=194.884s, table=20, n_packets=0, n_bytes=0, hard_timeout=300, idle_age=194, priority=1,vlan_tci=0x0306/0x0fff,dl_dst=5a:c6:4f:34:61:06 actions=load:0->NXM_OF_VLAN_TCI[],load:0x1ef->NXM_NX_TUN_ID[],output:24

  Due to the reason explained above, the time  for vm migration is
  increased. By monitoring the rule status on the tun bridge and the
  network connectivity, the network connectivity is restored after the
  rule of tun bridge is updated.

  Therefore, the time for vm migration can be reduced by updating the
  rule immediately.

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