Related Bugzilla: https://bu= gzil=3D la.redhat.com/show_bug.cgi?id=3D3D1213251

From: sokratis123k(a)outlook.com
To: users(a)ovirt.org
Subject: VM d= oesn=3D 't start after storage migration (Logical volume does not exist)
Date: F= =3D ri=3D2C 17 Apr 2015 10:41:11 +0300

=3D0A=3D =3D0A=3D =3D0A=3D

Hello=3D2C

I performed a storage migration of= a C=3D entOS 6 VM and while the migration was succesfull (based on the output in t= =3D he tasks tab on the bottom of the webadmin portal) the Disks on the VM's ta= =3D b weren't refreshed with the new Storage Domain information and remained lo= =3D cked.

I removed the lock by running "update images set imagestat= =3D us =3D3D 1 where imagestatus =3D3D 2=3D3B" on the database but the storage = domain=3D wasn't updated to the new one and kept the original location.

N= =3D ow I'm unable to start the VM probably because the disks have been migrated= =3D but the information on the database stills points on the old storage domai= =3D n.

The vdsm log throws the following error at VM startup:

Thread-887::ERROR::2015-04-17 10:08:11=3D2C831::task::866::Storage.Tas= kM=3D anager.Task::(_setError) Task=3D3D`7b51e15b-b04f-4f17-8096-882beffc1a6f`::U= ne=3D xpected error
Thread-887::ERROR::2015-04-17 10:08:11=3D2C953::dispatcher= ::=3D 76::Storage.Dispatcher::(wrapper) {'status': {'message': "Logical volume do= =3D es not exist: ('d3ec9e08-1e83-449e-b09d-dd50a4f7102f/d0870749-36b0-4ab2-91a= =3D 5-4743c690551a'=3D2C)"=3D2C 'code': 610}}
Thread-887::ERROR::2015-04-17 = 10:0=3D 8:11=3D2C975::vm::2331::vm.Vm::(_startUnderlyingVm) vmId=3D3D`1282c0ed-f753= -448=3D 4-bb4e-82d41febbba4`::The vm start process failed

Similarly the = =3D engine log throws the following error:

2015-04-17 09:39:42=3D2C1= 74=3D ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirecto= =3D r] (DefaultQuartzScheduler_Worker-94) [4c6a284] Correlation ID: null=3D2C C= al=3D l Stack: null=3D2C Custom Event ID: -1=3D2C Message: VM testvm is down with= err=3D or. Exit message: ('Failed to get size for volume %s'=3D2C 'd0870749-36b0-4= ab=3D 2-91a5-4743c690551a').
2015-04-17 09:39:42=3D2C175 INFO =3D3B [org.o= virt=3D .engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker= =3D -94) [4c6a284] Running on vds during rerun failed vm: null
2015-04-17 09= =3D :39:42=3D2C177 INFO =3D3B [org.ovirt.engine.core.vdsbroker.VdsUpdateRun= Time=3D Info] (DefaultQuartzScheduler_Worker-94) [4c6a284] VM testvm (1282c0ed-f753= =3D -4484-bb4e-82d41febbba4) is running in db and not running in VDS node01
= =3D 2015-04-17 09:39:42=3D2C178 INFO =3D3B [org.ovirt.engine.core.vdsbroker= .Vds=3D UpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-94) [4c6a284] add VM test= =3D vm to HA rerun treatment
2015-04-17 09:39:42=3D2C199 ERROR [org.ovirt.en= gi=3D ne.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-94) = =3D [4c6a284] Rerun vm 1282c0ed-f753-4484-bb4e-82d41febbba4. Called from vds no= =3D de01

How can I fix this? Do I have to edit the database? How can= =3D I find which is the correct logical volume associated with the VM?

= =3D
Thank you=3D2C

Sokratis

= =3D