Instance in anti-affinity group migrate from host1 to host2 success, then migrate back failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Incomplete
|
Undecided
|
Sahitya P |
Bug Description
Description
===========
Create an instance in anti-affinity group, then migrate this instance from one host to another success, but migrate back failed.
Steps to reproduce
==================
1. create anti-affinity group
+------
| Id | Name | Project Id | User Id | Policies | Members | Metadata |
+------
| 2f9cb321-
+------
2. create an instance in this group
nova boot --flavor 1 --image 480fc701-
3. migrate this instance success
nova migrate 974b3da6-
4. migrate again failed
nova migrate 974b3da6-
ERROR (BadRequest): No valid host was found. No valid host found for cold migrate (HTTP 400) (Request-ID: req-3fc9fa7a-
5. only have two compute_nodes.
nova hypervisor-list
+------
| ID | Hypervisor hostname | State | Status |
+------
| 4134c729-
| cade3580-
+------
Expected result
===============
migrate success because this anti-affinity group without other instance.
Actual result
=============
migrate failed in second times.
Environment
===========
1. Exact version of OpenStack you are running. See the following
Pike
2. Which hypervisor did you use?
Libvirt + KVM
3. Which networking type did you use?
Neutron with OpenVSwitch
Logs & Configs
==============
1. nova-scheduler
2019-01-14 19:23:23.555 18615 INFO nova.filters [req-3fc9fa7a-
2. request_spec's value changed when first migrate success
update source compute_node in request-spec's server_group_hosts when first migrate success.
tags: | added: scheduler |
Changed in nova: | |
assignee: | nobody → Sahitya P (sahityap) |
Changed in nova: | |
assignee: | Sahitya P (sahityap) → nobody |
assignee: | nobody → Sahitya P (sahityap) |
This is live migrate? or cold migrate?