[
https://issues.apache.org/jira/browse/CLOUDSTACK-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Girish Shilamkar updated CLOUDSTACK-5626:
-----------------------------------------
Description:
The test does the following:
1. Start a vm
2. Get a list of hosts available
3. Migrate the vm to some another hosts.
Sometimes and mostly in daily runs the migration fails with error:
'Cannot migrate VM, VM is already presnt on this host, please specify valid
destination host to migrate the VM"
I have confirmed that the testcase does not try to migrate to the same host on
which the vm is. And it is seen in the API call that the destination host is
indeed different from source host.
test_07_migrate_instance_in_network
(integration.component.test_vpc_vm_life_cycle.TestVMLifeCycleStoppedVPCVR):
DEBUG: Migrating VM-ID: 11f52df4-480e-480e-b7b7-635a65a79bc6 on Host:
1b2a97f4-1f76-4f9e-b1be-9b4138ae76aa to Host:
efac2d9e-e54a-468e-b09f-4afe1624bdcc
test_07_migrate_instance_in_network
(integration.component.test_vpc_vm_life_cycle.TestVMLifeCycleStoppedVPCVR):
DEBUG: sending GET request: migrateVirtualMachine {'hostid':
u'efac2d9e-e54a-468e-b09f-4afe1624bdcc', 'virtualmachineid': u'11f52df4-48
The details can be found in api-test.log attached.
This problem is consistently seen in daily run. But only for KVM. If I try to
reproduce this in my local setup, I am not able to.
was:
The test does the following:
1. Start a vm
2. Get a list of hosts available
3. Migrate the vm to some another hosts.
Sometimes and mostly in daily runs the migration fails with error:
'Cannot migrate VM, VM is already presnt on this host, please specify valid
destination host to migrate the VM"
I have confirmed that the testcase does not try to migrate to the same host on
which the vm is. And it is seen in the API call that the destination host is
indeed different from source host.
test_07_migrate_instance_in_network
(integration.component.test_vpc_vm_life_cycle.TestVMLifeCycleStoppedVPCVR):
DEBUG: Migrating VM-ID: 11f52df4-480e-480e-b7b7-635a65a79bc6 on Host:
1b2a97f4-1f76-4f9e-b1be-9b4138ae76aa to Host:
efac2d9e-e54a-468e-b09f-4afe1624bdcc
test_07_migrate_instance_in_network
(integration.component.test_vpc_vm_life_cycle.TestVMLifeCycleStoppedVPCVR):
DEBUG: sending GET request: migrateVirtualMachine {'hostid':
u'efac2d9e-e54a-468e-b09f-4afe1624bdcc', 'virtualmachineid': u'11f52df4-48
This problem is consistently seen in daily run. But only for KVM. If I try to
reproduce this in my local setup, I am not able to.
> [Automation] migrate instance tests are failing
> -----------------------------------------------
>
> Key: CLOUDSTACK-5626
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5626
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: xenserver 62
> advanced zone
> Reporter: Srikanteswararao Talluri
> Fix For: 4.3.0
>
> Attachments: api-test.log, mgmt.tar.gz
>
>
> The test does the following:
> 1. Start a vm
> 2. Get a list of hosts available
> 3. Migrate the vm to some another hosts.
> Sometimes and mostly in daily runs the migration fails with error:
> 'Cannot migrate VM, VM is already presnt on this host, please specify valid
> destination host to migrate the VM"
> I have confirmed that the testcase does not try to migrate to the same host
> on which the vm is. And it is seen in the API call that the destination host
> is indeed different from source host.
> test_07_migrate_instance_in_network
> (integration.component.test_vpc_vm_life_cycle.TestVMLifeCycleStoppedVPCVR):
> DEBUG: Migrating VM-ID: 11f52df4-480e-480e-b7b7-635a65a79bc6 on Host:
> 1b2a97f4-1f76-4f9e-b1be-9b4138ae76aa to Host:
> efac2d9e-e54a-468e-b09f-4afe1624bdcc
> test_07_migrate_instance_in_network
> (integration.component.test_vpc_vm_life_cycle.TestVMLifeCycleStoppedVPCVR):
> DEBUG: sending GET request: migrateVirtualMachine {'hostid':
> u'efac2d9e-e54a-468e-b09f-4afe1624bdcc', 'virtualmachineid': u'11f52df4-48
> The details can be found in api-test.log attached.
> This problem is consistently seen in daily run. But only for KVM. If I try to
> reproduce this in my local setup, I am not able to.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
