RE: VM Storage migration only works once not vice versa CS 4.3 Xen 6.2 SP1
Hi Sanjeev,
Thank you for response, yes the host from the new cluster can mount the primary
storage from the first cluster, I think this is the error
VM state transitted from :Stopped to Migrating with event:
StorageMigrationRequested
vm's original host id: 73 new host id: null host id before state transition:
null
Cheers
-Original Message-
From: Sanjeev Neelarapu [mailto:sanjeev.neelar...@citrix.com]
Sent: Monday, 25 August 2014 12:31 PM
To: users@cloudstack.apache.org; d...@cloudstack.apache.org
Subject: RE: VM Storage migration only works once not vice versa CS 4.3 Xen
6.2 SP1
Hi Amin,
There are no error messages in the log snippet you have provided.
Is the host in the 2nd cluster from which you are trying vm storage migration
(2nd time after successful migration) able to mount the primary storage in the
cluster1? If not you may have to resolve that issue. Otherwise open a defect.
Thanks,
Sanjeev
-Original Message-
From: Amin Samir [mailto:a...@opencloud.net.au]
Sent: Monday, August 25, 2014 7:21 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: VM Storage migration only works once not vice versa CS 4.3 Xen 6.2
SP1
Hello,
We have two clusters, the environment is as follows:
? CS Mgmt server 4.3 on CentOS 6.5
? Hypervisors Xen Server 6.2 SP1.
? One Zone, Two clusters with different two primary storage servers.
? Primary Secondary storage are NFS based.
When attempting to move a VM from one cluster to another, we succeed only the
first time, the VM and its files are moved to a new hypervisor and new storage
server in the new cluster, however when attempting to migrate the VM to the
original cluster, host, and original storage, the migration fails, so it is
only one time migration.
The logs are as follows, we would appreciate if someone has faced this issue
before, it is very helpful feature in cloud stack to migrate across clusters
and storage servers, but it seems it is not working, cause we simulated the
environment on CS 4.3 from scratch installation and the behaviour is the same.
/mnt/DATA/VM-SEC-01/volumes/2/1071 is not being created.
2014-08-21 11:37:40,671 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-21:ctx-da934e40 ctx-fb603895) submit async job-10947, details:
AsyncJobVO {id:10947, userId: 2, accountId:
2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:w6C9EF9N9Xi0AhEXZ3Cdc9nQNkI\u003d,virtu
almachineid:ae028abb-4181-49fb-913f-bda34f77d792,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:098d4f7a-a040-3462-add1-d618d6ec53c1,httpmethod:GET,_:1408592259844,
ctxAccountId:2,ctxStartEventId:1088984}, cmdVersion: 0, status:
IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid:
53350633438879, completeMsid: null, lastUpda
ted: null, lastPolled: null, created: null}
2014-08-21 11:37:40,671 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-14:ctx-57b36727) Add job-10947 into job monitoring
2014-08-21 11:37:40,671 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-14:ctx-57b36727) Executing AsyncJobVO {id:10947, userId: 2,
accountId: 2, instanceType: None, instanceId: nu
ll, cmd: org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:w6C9EF9N9Xi0AhEXZ3Cdc9nQNkI\u003d,virtualmachineid:ae028abb-4181-49fb-913f
-bda34f77d792,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:098d4f7a-a040-3462-add1-d618d6ec53c1,httpmethod:GET,_:1408592259844,ctxAccountId:2,ctxStartEventId:
1088984}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode:
0, result: null, initMsid: 53350633438879, completeMsid: null, lastUpdated:
null, lastPolled: null, created:
null}
2014-08-21 11:37:40,672 DEBUG [c.c.a.ApiServlet] (catalina-exec-21:ctx-da934e40
ctx-fb603895) ===END=== 103.4.132.4 -- GET
command=migrateVirtualMachinestorageid=098d4f7a-a040-3462-ad
d1-d618d6ec53c1virtualmachineid=ae028abb-4181-49fb-913f-bda34f77d792response=jsonsessionkey=w6C9EF9N9Xi0AhEXZ3Cdc9nQNkI%3D_=1408592259844
2014-08-21 11:37:40,738 DEBUG [c.c.c.CapacityManagerImpl]
(Job-Executor-14:ctx-57b36727 ctx-fb603895) VM state transitted from :Stopped
to Migrating with event: StorageMigrationRequested
vm's original host id: 73 new host id: null host id before state transition:
null
2014-08-21 11:37:40,943 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Job-Executor-14:ctx-57b36727 ctx-fb603895) copyAsync inspecting src type
VOLUME copyAsync inspecting dest type VOLUME
2014-08-21 11:37:40,946 DEBUG [o.a.c.s.c.a.StorageCacheRandomAllocator]
(Job-Executor-14:ctx-57b36727 ctx-fb603895) Can't find staging storage in zone:
1
2014-08-21 11:37:41,092 DEBUG [c.c.a.t.Request] (Job-Executor-14:ctx-57b36727
ctx-fb603895) Seq 73-1469252089: Sending { Cmd , MgmtId: 53350633438879, via:
73(XEN-08), Ver: v1, Flags: 1
00011
RE: VM Storage migration only works once not vice versa CS 4.3 Xen 6.2 SP1
Hi Amin,
There are no error messages in the log snippet you have provided.
Is the host in the 2nd cluster from which you are trying vm storage migration
(2nd time after successful migration) able to mount the primary storage in the
cluster1? If not you may have to resolve that issue. Otherwise open a defect.
Thanks,
Sanjeev
-Original Message-
From: Amin Samir [mailto:a...@opencloud.net.au]
Sent: Monday, August 25, 2014 7:21 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: VM Storage migration only works once not vice versa CS 4.3 Xen 6.2
SP1
Hello,
We have two clusters, the environment is as follows:
? CS Mgmt server 4.3 on CentOS 6.5
? Hypervisors Xen Server 6.2 SP1.
? One Zone, Two clusters with different two primary storage servers.
? Primary Secondary storage are NFS based.
When attempting to move a VM from one cluster to another, we succeed only the
first time, the VM and its files are moved to a new hypervisor and new storage
server in the new cluster, however when attempting to migrate the VM to the
original cluster, host, and original storage, the migration fails, so it is
only one time migration.
The logs are as follows, we would appreciate if someone has faced this issue
before, it is very helpful feature in cloud stack to migrate across clusters
and storage servers, but it seems it is not working, cause we simulated the
environment on CS 4.3 from scratch installation and the behaviour is the same.
/mnt/DATA/VM-SEC-01/volumes/2/1071 is not being created.
2014-08-21 11:37:40,671 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-21:ctx-da934e40 ctx-fb603895) submit async job-10947, details:
AsyncJobVO {id:10947, userId: 2, accountId:
2, instanceType: None, instanceId: null, cmd:
org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:w6C9EF9N9Xi0AhEXZ3Cdc9nQNkI\u003d,virtu
almachineid:ae028abb-4181-49fb-913f-bda34f77d792,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:098d4f7a-a040-3462-add1-d618d6ec53c1,httpmethod:GET,_:1408592259844,
ctxAccountId:2,ctxStartEventId:1088984}, cmdVersion: 0, status:
IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid:
53350633438879, completeMsid: null, lastUpda
ted: null, lastPolled: null, created: null}
2014-08-21 11:37:40,671 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-14:ctx-57b36727) Add job-10947 into job monitoring
2014-08-21 11:37:40,671 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-14:ctx-57b36727) Executing AsyncJobVO {id:10947, userId: 2,
accountId: 2, instanceType: None, instanceId: nu
ll, cmd: org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdInfo:
{response:json,sessionkey:w6C9EF9N9Xi0AhEXZ3Cdc9nQNkI\u003d,virtualmachineid:ae028abb-4181-49fb-913f
-bda34f77d792,cmdEventType:VM.MIGRATE,ctxUserId:2,storageid:098d4f7a-a040-3462-add1-d618d6ec53c1,httpmethod:GET,_:1408592259844,ctxAccountId:2,ctxStartEventId:
1088984}, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode:
0, result: null, initMsid: 53350633438879, completeMsid: null, lastUpdated:
null, lastPolled: null, created:
null}
2014-08-21 11:37:40,672 DEBUG [c.c.a.ApiServlet] (catalina-exec-21:ctx-da934e40
ctx-fb603895) ===END=== 103.4.132.4 -- GET
command=migrateVirtualMachinestorageid=098d4f7a-a040-3462-ad
d1-d618d6ec53c1virtualmachineid=ae028abb-4181-49fb-913f-bda34f77d792response=jsonsessionkey=w6C9EF9N9Xi0AhEXZ3Cdc9nQNkI%3D_=1408592259844
2014-08-21 11:37:40,738 DEBUG [c.c.c.CapacityManagerImpl]
(Job-Executor-14:ctx-57b36727 ctx-fb603895) VM state transitted from :Stopped
to Migrating with event: StorageMigrationRequested
vm's original host id: 73 new host id: null host id before state transition:
null
2014-08-21 11:37:40,943 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Job-Executor-14:ctx-57b36727 ctx-fb603895) copyAsync inspecting src type
VOLUME copyAsync inspecting dest type VOLUME
2014-08-21 11:37:40,946 DEBUG [o.a.c.s.c.a.StorageCacheRandomAllocator]
(Job-Executor-14:ctx-57b36727 ctx-fb603895) Can't find staging storage in zone:
1
2014-08-21 11:37:41,092 DEBUG [c.c.a.t.Request] (Job-Executor-14:ctx-57b36727
ctx-fb603895) Seq 73-1469252089: Sending { Cmd , MgmtId: 53350633438879, via:
73(XEN-08), Ver: v1, Flags: 1
00011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:86417b6e-3fda-476e-b4d1-3bc77a67be89,volumeType:ROOT
,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:1a07254a-c9d4-3ae0-8090-461e6597d818,id:221,poolType:NetworkFilesystem,host:10.8.1.40,path:/mn
t/DRIVE/DATA,port:2049,url:NetworkFilesystem://10.8.1.40//mnt/DRIVE/DATA/?ROLE=PrimarySTOREUUID=1a07254a-c9d4-3ae0-8090-461e6597d818}},name:ROOT-710,size:42949672960,path
