yahoo-eng-team team mailing list archive

[chengsheng <1903931@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When calling the vm live migration through the API, the target host is
specified, but the force parameters are not added. If the micro version
of the api is not specified, the migration becomes a force migration.

When the service of the target host is set to be disabled, two situations will occur:
1. When the micro version is not specified, the live migration is successful.
2. When the micro version is specified and the micro version is greater than 2.30, the live migration fails. This is because the target host is selected through the scheduler at this time, but the target host has been disabled.

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

Title:
  live migration that does not specify a micro version becomes a force
  migration

Status in OpenStack Compute (nova):
  New

Bug description:
  When calling the vm live migration through the API, the target host is
  specified, but the force parameters are not added. If the micro
  version of the api is not specified, the migration becomes a force
  migration.

  When the service of the target host is set to be disabled, two situations will occur:
  1. When the micro version is not specified, the live migration is successful.
  2. When the micro version is specified and the micro version is greater than 2.30, the live migration fails. This is because the target host is selected through the scheduler at this time, but the target host has been disabled.

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