← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1402477] [NEW] Live migration of volume backed instances broken because the table of block_device_mapping was updated incorrect

 

Public bug reported:

1、 Live migration of volume backed instances
2、at pre_live_migration function,  the table of block_device_mapping has been updated as destination  host volume lun information
3、at /nova/compute/manager.py  _post_live_migration function, when call  the funfunction 
     block_device_info = self._get_instance_block_device_info( ctxt, instance, bdms) , because the  Parameters is incorrect , the 
     table of block_device_mapping will be changed as the source host volume lun information. 
4、the next step ,when run the function /nova/compute/manager.py  post_live_migration_at_destination ,will query volume lun connection from the table of block_device_mapping, but  the table has been updated as  source host volume lun information,so
the destination  host  run the under function will failed. :
          self.volume_driver_method('connect_volume',
                                               connection_info,
                                               disk_dev)

** 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/1402477

Title:
   Live migration of volume backed instances broken because  the table
  of block_device_mapping was updated incorrect

Status in OpenStack Compute (Nova):
  New

Bug description:
  1、 Live migration of volume backed instances
  2、at pre_live_migration function,  the table of block_device_mapping has been updated as destination  host volume lun information
  3、at /nova/compute/manager.py  _post_live_migration function, when call  the funfunction 
       block_device_info = self._get_instance_block_device_info( ctxt, instance, bdms) , because the  Parameters is incorrect , the 
       table of block_device_mapping will be changed as the source host volume lun information. 
  4、the next step ,when run the function /nova/compute/manager.py  post_live_migration_at_destination ,will query volume lun connection from the table of block_device_mapping, but  the table has been updated as  source host volume lun information,so
  the destination  host  run the under function will failed. :
            self.volume_driver_method('connect_volume',
                                                 connection_info,
                                                 disk_dev)

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


Follow ups

References