Nova migration are working through admin network. We should use nova/migration or management network role for this.
Deploy environment:
1 controller
2 or more compute nodes
Deploy is successful. Go to controller node. Login to mysql:
mysql> use nova;
mysql> SELECT id, created_at, updated_at, hypervisor_hostname, host_ip FROM compute_nodes;
+----+---------------------+---------------------+---------------------+-----------+
| id | created_at | updated_at | hypervisor_hostname | host_ip |
+----+---------------------+---------------------+---------------------+-----------+
| 1 | 2015-12-23 13:07:32 | 2015-12-23 15:15:53 | node-1.domain.tld | 10.20.0.4 |
| 2 | 2015-12-23 14:09:55 | 2015-12-23 15:04:24 | node-2.domain.tld | 10.20.0.5 |
+----+---------------------+---------------------+---------------------+-----------+
Nova services are registered with IPs from admin network. This is incorrect. They should be registered with IPs from nova/migration or management network roles. To fix this we need to set 'my_ip' parameter on each compute node.
To check that migration really goes through admin network, you can block connection through admin network between computes and try to migrate instance.
MOS-Nova team, please confirm the issue and reassign it to mos-puppet team to fix 'my_ip' parameter.
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "8.0"
api: "1.0"
build_number: "318"
build_id: "318"
fuel-nailgun_sha: "ec25ae8df28e1f1d87da653c5aab2711dff729f6"
python-fuelclient_sha: "7c7a756fb6a3d091851c060003a2965c67aa353d"
fuel-agent_sha: "d354cbe61b055db848a15ce66fb7ae92178d2c0a"
fuel-nailgun-agent_sha: "a33a58d378c117c0f509b0e7badc6f0910364154"
astute_sha: "c56dfde2da034151a7e707b381c4cf9d213b4ba2"
fuel-library_sha: "bcc3d042a47547f6ad826360a85ef21dcaf25882"
fuel-ostf_sha: "b2ebf15a3530b5c7b57707acf8642c1c3ac71bd8"
fuel-mirror_sha: "8100acb3a566358d0d4ecc66de32d39626263028"
fuelmenu_sha: "2942a85796d37f09ba8c8c6d762d8813292cf0d4"
shotgun_sha: "cacb93cbc28910ff0dc38f30a855efa9af50d8ce"
network-checker_sha: "d443ef47abeda58d319bc8d33d5005dd09440a02"
fuel-upgrade_sha: "718aa3d7021fee2970f0fa6791cf5188578cc516"
fuelmain_sha: "3faa824728ce60734abe602ff3778976f8a16eed"
Ivan, you are right, we must configure 'my-ip' option explicitly to effectively specify the network to be used for offline VM migration.