cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-5626) [Automation] migrate instance tests are failing
Date Mon, 10 Mar 2014 05:49:43 GMT


ASF subversion and git services commented on CLOUDSTACK-5626:

Commit 3b3ae024591fae4db9a6ca991d4838d98b96154e in cloudstack's branch refs/heads/master from
[;h=3b3ae02 ]

CLOUDSTACK-5626: Simplifying VM Migrate code

Signed-off-by: SrikanteswaraRao Talluri <>

> [Automation] migrate instance tests are failing
> -----------------------------------------------
>                 Key: CLOUDSTACK-5626
>                 URL:
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.3.0
>         Environment: xenserver 62
> advanced zone
>            Reporter: Srikanteswararao Talluri
>            Assignee: Girish Shilamkar
>             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

View raw message