| 2014-04-04 13:52:32 |
Ankit Agrawal |
description |
If the vm fails to spawn on the nova compute node where it was suppose to run, then it reschedules to run the vm on the another compute node. After the vm is created successfully on the another node, you will notice that VM is assigned 2 fixed ip addresses.
Expected output: only one fixed ip address should be assigned to a VM.
Actual output:
openstack@development-009:/opt/stack/nova/nova/compute$ nova list
+--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+
| 42016c47-40c3-4562-b2b5-d3c8199cc4e6 | nova-42016c47-40c3-4562-b2b5-d3c8199cc4e6 | ACTIVE | - | Running | private=10.0.0.81, 10.0.0.82 |
+--------------------------------------+-------------------------------------------+--------+------------+-------------+------------------------------+
To reproduce this issue, you will need to explicitly raise Exception from compute/manafger.py->_spawn method. |
If the vm fails to spawn on the nova compute node where it was suppose to run, then it reschedules to run the vm on the another compute node.
Network of VM is deleted before trying to re-schedule it on another host. But system_metadata of instance is not updated ('network_allocated' is not
set to False). We should also update system_metadata after network is deleted from VM.
While allocating network to instance we set system_metadata 'network_allocated' as True, but while deallocating network we do not set 'network_allocated'
to False. |
|
