yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

I'm just going to invalidate this since if you're using microversion <
2.34 you'll get a 400 because of the UnableToMigrateToSelf error from
conductor and if you're using >= 2.34 you'll get a 202 response but the
operation will fail and a fault will be recorded, there would just be
more work to do, e.g. swapping allocations, calling the scheduler,
reverting the allocation swap, etc. As long as the instance isn't put
into ERROR state though we're probably OK.

** Changed in: nova
     Assignee: jichenjc (jichenjc) => (unassigned)

** Changed in: nova
       Status: In Progress => 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/1714235

Title:
  os-migrateLive API does not restrict one from trying to migrate to the
  original host

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  This is purely based on code inspection, but the compute API method
  'evacuate' does not check if the specified host (if there was one) is
  different from instance.host. It checks if the service is up on that
  host, which could be down and you can still specify the instance.host.

  Eventually the compute API will RPC cast to conductor task manager
  which will fail with an RPC error trying to RPC cast to the
  ComputeManager.rebuild_instance method on the compute service, which
  is down.

  The bug here is that instead of getting an obvious 400 error from the
  API, you're left with not much for details when it fails. There should
  be an instance action and finish event, but only the admin can see the
  traceback in the event. Also, the instance.task_state would be left in
  'rebuilding' state, and would require it to be reset to use the
  instance again.

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