yahoo-eng-team team mailing list archive

[Artom Lifshitz <1995714@xxxxxxxxxxxxxxxxxx>]

Cold migration assumes that the source compute host is up (and I think
has checks in the code for that). A cold migration will fail if the
source compute host is actually down and not disabled. The correct thing
to do in that case is an evacuation.

** Changed in: nova
       Status: New => Invalid

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

Title:
  cold migration shouldn't spin up the vm ins a resize step

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  disable a compute node

  run migration on a vm not running, it will still have to start on that
  compute node to do resize...

  next imagine that the compute node has gone down, why can't it just do
  a new scheduling and start running on a existing/not-disabled node?

  this is with shared storage btw...

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