yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

In multinode devstack I had an instance running on one node and tried
running "nova migrate <uuid>".  The operation started, but then the
instance went into an error state with the following fault:

{"message": "Unable to migrate instance (2bbdab8e-
3a83-43a4-8c47-ce57b653e43e) to current host (fedora-1.novalocal).",
"code": 400, "created": "2019-03-08T19:59:09Z"}

Logically, I think that even if "resize to same host" is enabled, for a
"migrate" operation we should remove the current host from
consideration.  We know it's going to fail, and it doesn't make sense
anyways.

Also, it would probably make sense to make "migrate" work like "live
migration" which removes the current host from consideration.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: compute

** Summary changed:

- in devstack, "nova migrate <uuid>" can try to migrate to the same host
+ in devstack, "nova migrate <uuid>" will try to migrate to the same host (and then fail)

** Description changed:

  In multinode devstack I had an instance running on one node and tried
  running "nova migrate <uuid>".  The operation started, but then the
  instance went into an error state with the following fault:
  
  {"message": "Unable to migrate instance (2bbdab8e-
  3a83-43a4-8c47-ce57b653e43e) to current host (fedora-1.novalocal).",
  "code": 400, "created": "2019-03-08T19:59:09Z"}
  
  Logically, I think that even if "resize to same host" is enabled, for a
  "migrate" operation we should remove the current host from
  consideration.  We know it's going to fail, and it doesn't make sense
  anyways.
+ 
+ Also, it would probably make sense to make "migrate" work like "live
+ migration" which removes the current host from consideration.

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

Title:
  in devstack, "nova migrate <uuid>" will try to migrate to the same
  host (and then fail)

Status in OpenStack Compute (nova):
  New

Bug description:
  In multinode devstack I had an instance running on one node and tried
  running "nova migrate <uuid>".  The operation started, but then the
  instance went into an error state with the following fault:

  {"message": "Unable to migrate instance (2bbdab8e-
  3a83-43a4-8c47-ce57b653e43e) to current host (fedora-1.novalocal).",
  "code": 400, "created": "2019-03-08T19:59:09Z"}

  Logically, I think that even if "resize to same host" is enabled, for
  a "migrate" operation we should remove the current host from
  consideration.  We know it's going to fail, and it doesn't make sense
  anyways.

  Also, it would probably make sense to make "migrate" work like "live
  migration" which removes the current host from consideration.

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