yahoo-eng-team team mailing list archive

[Gregory Cunha <gregory.cunha@xxxxxxxxxxxxxxx>]

Public bug reported:

During the live_migration, if a InvalidSharedStorage is raised, the VM stay in MIGRATING state.
The sequence of calls between services is the following (the request is a live_migration from <<Compute src>> to <<Compute dest>>):
<<Scheduler>> (rpc call)-> <<Compute dest>> : check_can_live_migrate_destination
<<Compute dest>> (rpc call) -> <<Compute src>> : check_can_live_migrate_source

Exception InvalidSharedStorage raised by <<Compute src>> is deserialised by <<Compute dest>> as InvalidSharedStorage_Remote. 
Exception InvalidSharedStorage_Remote raised by <<Compute dest>> is deserialised by <<Scheduler>> as RemoteError.
So the rollback on status is not done by <<Scheduler>>

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

Title:
  If live_migration failed, VM stay in state "MIGRATING"

Status in OpenStack Compute (Nova):
  New

Bug description:
  During the live_migration, if a InvalidSharedStorage is raised, the VM stay in MIGRATING state.
  The sequence of calls between services is the following (the request is a live_migration from <<Compute src>> to <<Compute dest>>):
  <<Scheduler>> (rpc call)-> <<Compute dest>> : check_can_live_migrate_destination
  <<Compute dest>> (rpc call) -> <<Compute src>> : check_can_live_migrate_source

  Exception InvalidSharedStorage raised by <<Compute src>> is deserialised by <<Compute dest>> as InvalidSharedStorage_Remote. 
  Exception InvalidSharedStorage_Remote raised by <<Compute dest>> is deserialised by <<Scheduler>> as RemoteError.
  So the rollback on status is not done by <<Scheduler>>

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