← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1880389] [NEW] lost net connection when live migration

 

Public bug reported:

Description
===========
I find VM will lost net connection when live migration. 

I enabled the live_migration_wait_for_vif_plug and set
vif_plugging_timeout=120.

My openstack version is queens, and I used linux bridge as my L2 plugin.
and the physical adapter of my host I did bond0 mode.

when the live migration done, I found the ping of VM is broken down, and
I use tcpdump to catch the package, I found the package from switch
still reach the destination host.


Steps to reproduce
==================
1. enable the live_migration_wait_for_vif_plug = True and vif_plugging_timeout = 120 (remeber restart the linuxbridge-agent in source and destination host)
2. created a new VM ,and then ping the VM which created in step
3. do the live migration action.(before live migration you need to make sure the vlan sub_interface of the network which vm attached not in the dest host. )
4. when the processing of live migration, U will found the ping to the VM was broken down.

Expected result
===============
the ping should not broken down when live migration. 

Actual result
=============
the ping was broken down. and the ping package from the physic switch was still set to the source.


Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/

   queens

2. Which hypervisor did you use?
    
   Libvirt + KVM

3. Which storage type did you use?
   ceph
   

4. Which networking type did you use?
   Neutron with LinuxBirdge
   the network type of VM  is Vlan type.


And I found the time of 5 RARP from VM is before the time of the vlan
sub interface insert to the linuxbridge bridge when live migration.
maybe this will help us to make sure the problem I found.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1880389

Title:
  lost net connection  when live migration

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  I find VM will lost net connection when live migration. 

  I enabled the live_migration_wait_for_vif_plug and set
  vif_plugging_timeout=120.

  My openstack version is queens, and I used linux bridge as my L2
  plugin. and the physical adapter of my host I did bond0 mode.

  when the live migration done, I found the ping of VM is broken down,
  and I use tcpdump to catch the package, I found the package from
  switch still reach the destination host.

  
  Steps to reproduce
  ==================
  1. enable the live_migration_wait_for_vif_plug = True and vif_plugging_timeout = 120 (remeber restart the linuxbridge-agent in source and destination host)
  2. created a new VM ,and then ping the VM which created in step
  3. do the live migration action.(before live migration you need to make sure the vlan sub_interface of the network which vm attached not in the dest host. )
  4. when the processing of live migration, U will found the ping to the VM was broken down.

  Expected result
  ===============
  the ping should not broken down when live migration. 

  Actual result
  =============
  the ping was broken down. and the ping package from the physic switch was still set to the source.

  
  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

     queens

  2. Which hypervisor did you use?
      
     Libvirt + KVM

  3. Which storage type did you use?
     ceph
     

  4. Which networking type did you use?
     Neutron with LinuxBirdge
     the network type of VM  is Vlan type.


  And I found the time of 5 RARP from VM is before the time of the vlan
  sub interface insert to the linuxbridge bridge when live migration.
  maybe this will help us to make sure the problem I found.

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


Follow ups