
From: sokratis123k@outlook.com<br>To: users@ovirt.org<br>Subject: VM doesn= 't start after storage migration (Logical volume does not exist)<br>Date: F= ri=2C 17 Apr 2015 10:41:11 +0300<br><br>=0A= =0A= <style><!--=0A= .ExternalClass .ecxhmmessage P {=0A=
--_35e1d6e4-b29c-439f-9397-edf5713d5067_ Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Related Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=3D1213251 From: sokratis123k@outlook.com To: users@ovirt.org Subject: VM doesn't start after storage migration (Logical volume does not = exist) Date: Fri=2C 17 Apr 2015 10:41:11 +0300 =0A= =0A= =0A= Hello=2C I performed a storage migration of a CentOS 6 VM and while the migration wa= s succesfull (based on the output in the tasks tab on the bottom of the web= admin portal) the Disks on the VM's tab weren't refreshed with the new Stor= age Domain information and remained locked. I removed the lock by running "update images set imagestatus =3D 1 where im= agestatus =3D 2=3B" on the database but the storage domain wasn't updated t= o the new one and kept the original location. Now I'm unable to start the VM probably because the disks have been migrate= d but the information on the database stills points on the old storage doma= in. The vdsm log throws the following error at VM startup: Thread-887::ERROR::2015-04-17 10:08:11=2C831::task::866::Storage.TaskManage= r.Task::(_setError) Task=3D`7b51e15b-b04f-4f17-8096-882beffc1a6f`::Unexpect= ed error Thread-887::ERROR::2015-04-17 10:08:11=2C953::dispatcher::76::Storage.Dispa= tcher::(wrapper) {'status': {'message': "Logical volume does not exist: ('d= 3ec9e08-1e83-449e-b09d-dd50a4f7102f/d0870749-36b0-4ab2-91a5-4743c690551a'= =2C)"=2C 'code': 610}} Thread-887::ERROR::2015-04-17 10:08:11=2C975::vm::2331::vm.Vm::(_startUnder= lyingVm) vmId=3D`1282c0ed-f753-4484-bb4e-82d41febbba4`::The vm start proces= s failed Similarly the engine log throws the following error: 2015-04-17 09:39:42=2C174 ERROR [org.ovirt.engine.core.dal.dbbroker.auditlo= ghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-94) [4c6a284] Co= rrelation ID: null=2C Call Stack: null=2C Custom Event ID: -1=2C Message: V= M testvm is down with error. Exit message: ('Failed to get size for volume = %s'=2C 'd0870749-36b0-4ab2-91a5-4743c690551a'). 2015-04-17 09:39:42=2C175 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateR= unTimeInfo] (DefaultQuartzScheduler_Worker-94) [4c6a284] Running on vds dur= ing rerun failed vm: null 2015-04-17 09:39:42=2C177 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateR= unTimeInfo] (DefaultQuartzScheduler_Worker-94) [4c6a284] VM testvm (1282c0e= d-f753-4484-bb4e-82d41febbba4) is running in db and not running in VDS node= 01 2015-04-17 09:39:42=2C178 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateR= unTimeInfo] (DefaultQuartzScheduler_Worker-94) [4c6a284] add VM testvm to H= A rerun treatment 2015-04-17 09:39:42=2C199 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateR= unTimeInfo] (DefaultQuartzScheduler_Worker-94) [4c6a284] Rerun vm 1282c0ed-= f753-4484-bb4e-82d41febbba4. Called from vds node01 How can I fix this? Do I have to edit the database? How can I find which is= the correct logical volume associated with the VM? Thank you=2C Sokratis = --_35e1d6e4-b29c-439f-9397-edf5713d5067_ Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable <html> <head> <style><!-- .hmmessage P { margin:0px=3B padding:0px } body.hmmessage { font-size: 12pt=3B font-family:Calibri } --></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'>Related Bugzilla: https://bugzil= la.redhat.com/show_bug.cgi?id=3D1213251<br><br><div><hr id=3D"stopSpelling"= padding:0px=3B=0A= }=0A= =0A= .ExternalClass body.ecxhmmessage {=0A= font-size:12pt=3B=0A= font-family:Calibri=3B=0A= }=0A= =0A= --></style>=0A= <div dir=3D"ltr">Hello=2C<br><br><br>I performed a storage migration of a C= entOS 6 VM and while the migration was succesfull (based on the output in t= he tasks tab on the bottom of the webadmin portal) the Disks on the VM's ta= b weren't refreshed with the new Storage Domain information and remained lo= cked.<br><br><br>I removed the lock by running "update images set imagestat= us =3D 1 where imagestatus =3D 2=3B" on the database but the storage domain= wasn't updated to the new one and kept the original location.<br><br><br>N= ow I'm unable to start the VM probably because the disks have been migrated= but the information on the database stills points on the old storage domai= n.<br><br><br>The vdsm log throws the following error at VM startup:<br><br=
<br>Thread-887::ERROR::2015-04-17 10:08:11=2C831::task::866::Storage.TaskM= anager.Task::(_setError) Task=3D`7b51e15b-b04f-4f17-8096-882beffc1a6f`::Une= xpected error<br>Thread-887::ERROR::2015-04-17 10:08:11=2C953::dispatcher::= 76::Storage.Dispatcher::(wrapper) {'status': {'message': "Logical volume do= es not exist: ('d3ec9e08-1e83-449e-b09d-dd50a4f7102f/d0870749-36b0-4ab2-91a= 5-4743c690551a'=2C)"=2C 'code': 610}}<br>Thread-887::ERROR::2015-04-17 10:0= 8:11=2C975::vm::2331::vm.Vm::(_startUnderlyingVm) vmId=3D`1282c0ed-f753-448= 4-bb4e-82d41febbba4`::The vm start process failed<br><br><br>Similarly the = engine log throws the following error:<br><br><br>2015-04-17 09:39:42=2C174= ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirecto= r] (DefaultQuartzScheduler_Worker-94) [4c6a284] Correlation ID: null=2C Cal= l Stack: null=2C Custom Event ID: -1=2C Message: VM testvm is down with err= or. Exit message: ('Failed to get size for volume %s'=2C 'd0870749-36b0-4ab= 2-91a5-4743c690551a').<br>2015-04-17 09:39:42=2C175 INFO =3B [org.ovirt= .engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker= -94) [4c6a284] Running on vds during rerun failed vm: null<br>2015-04-17 09= :39:42=2C177 INFO =3B [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTime= Info] (DefaultQuartzScheduler_Worker-94) [4c6a284] VM testvm (1282c0ed-f753= -4484-bb4e-82d41febbba4) is running in db and not running in VDS node01<br>= 2015-04-17 09:39:42=2C178 INFO =3B [org.ovirt.engine.core.vdsbroker.Vds= UpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-94) [4c6a284] add VM test= vm to HA rerun treatment<br>2015-04-17 09:39:42=2C199 ERROR [org.ovirt.engi= ne.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-94) = [4c6a284] Rerun vm 1282c0ed-f753-4484-bb4e-82d41febbba4. Called from vds no= de01<br><br><br>How can I fix this? Do I have to edit the database? How can= I find which is the correct logical volume associated with the VM?<br><br>= <br>Thank you=2C<br><br><br>Sokratis<br> </div></div> = </div></body> </html>=
--_35e1d6e4-b29c-439f-9397-edf5713d5067_--