live migration that does not specify a micro version becomes a force migration
Bug #1903931 reported by
chengsheng
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Undecided
|
chengsheng | ||
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.
| Changed in nova: | |
| assignee: | nobody → chengsheng (chengsheng) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | New → In Progress |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/