yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => liberty-rc1

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

Title:
  Fail early when live-migrate with block-migration and bdm

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  If user do live-migration with  block migrate and  mapped volumes,
  user won't get an exception in nova-api.

  This exception will raise in nova-compute node, so user need to check
  log on compute node to tell why

  he/she trigger a live-migration but the instance is still in running
  state.

  Migration error: Cannot block migrate instance 41b1d849-6a29-448e-
  8ace-4f4750514d72 with mapped volumes

  
  We can make this happen early when doing can-live-migration-source/destination etc..

  by doing this, user will get the exception in nova-api this will bring
  good user experience, and besides

  if we raise this exception early , then nova won't do pre-live-
  migration and _rollback_live_migration.

  and it will partially fix
  https://bugs.launchpad.net/nova/+bug/1457291

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