[jira] [Commented] (CLOUDSTACK-5660) [Hyper-v] Migrate vm live migration succeeds but throws error as ""Failed to migrate the system vm""

["Devdeep Singh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877305#comment-13877305 ] 

Devdeep Singh commented on CLOUDSTACK-5660:
-------------------------------------------

The issue is not hyper-v specific. The UserVmManager::migrateVirtualMachine function is called by migrate system vm cmd. After migration is successful it looks up for the vm entry in uservmdao table and fails. System vm entries are only in vm_instance table and not user_vm table. Probably this change introduced the issue e99a1ef1d947ae2161cd64f97a089ef6f042a59e. 

We cannot change the look from uservmdao to vminstancedao because migrate vm cmd (not migrate system vm cmd) expects a uservmvo to be returned by UserVmManager::migrateVirtualMachine function.

Removing the Hyper-v tag and updated the bug description.

> [Hyper-v] Migrate vm live migration succeeds but throws error as ""Failed to migrate the system vm""
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5660
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5660
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller
>    Affects Versions: 4.3.0
>         Environment: Latest build from 4.3 branch with commit:
> bf7601e9b86b7ea66026ac3ac94cd145e9912864
>            Reporter: Sanjeev N
>            Assignee: Devdeep Singh
>             Fix For: 4.3.0
>
>
> [Hyper-v] Migrate vm live migration succeeds but throws error as ""Failed to migrate the system vm""
> Steps to Reproduce:
> ================
> 1.Bring up CS in advanced zone with at-least two hyper-v hosts in the cluster.
> 2.Deploy one guest vm with default cent os template
> 3.Live Migrate any vm (system /guest ) to another host.
> Result:
> ======
> VM Migration to another host succeeds but the migrate job retuns failure as follows :"2013-12-27 19:19:49,143 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-15:ctx-9065306c) Complete async job-19, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Failed to migrate the system vm"}
> 2013-12-27 19:19:49,208 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-15:ctx-9065306c) Done executing org.apache.cloudstack.api.command.admin.systemvm.MigrateSystemVMCmd for job-19"
> Does not throw any exception but throws error in UI and MS log . This might confuse the user.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)