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 => grizzly-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/1100462

Title:
  Instance task_state being left as migrating after InvalidSharedStorage
  error

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  If a live-migration fails due to an InvalidSharedStorage exception, or
  other pre-migration checks failing, the live migration is never
  attempted and the task_state is left as 'migrating' for the instance.
  This leaves the instance in a somewhat broken state and future
  requests on the instance fail such as pause, suspend, or stop. This
  behavior was changed between essex and folsom. Essex would not set the
  task_state to migrating if the pre-checks failed. Folsom sets the
  task_state to migrating before the pre-check are made and then do not
  clear the task_state if the pre-checks fail. I believe the current
  master would have the same behavior but I haven't tested. It seems
  that the instance task_state should be reset to None if the pre-
  migration checks fail.

  This was discovered against folsom (commit
  4bfc8f1165b05c2cc7c5506641b9b85fa8e1e144) and using devstack as a test
  environment.

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