Hello=3D2C

I perf= ormed =3D a storage migration of a CentOS 6 VM and while the migration was succesfull= =3D (based on the output in the tasks tab on the bottom of the webadmin portal= =3D ) the Disks on the VM's tab weren't refreshed with the new Storage Domain i= =3D nformation and remained locked.

I removed the lock by running "u= =3D pdate images set imagestatus =3D3D 1 where imagestatus =3D3D 2=3D3B" on the= datab=3D ase but the storage domain wasn't updated to the new one and kept the origi= =3D nal location.

Now I'm unable to start the VM probably because th= =3D e disks have been migrated but the information on the database stills point= =3D s on the old storage domain.

The vdsm log throws the following e= =3D rror at VM startup:

Thread-887::ERROR::2015-04-17 10:08:11=3D2C8= 31=3D ::task::866::Storage.TaskManager.Task::(_setError) Task=3D3D`7b51e15b-b04f-= 4f=3D 17-8096-882beffc1a6f`::Unexpected error
Thread-887::ERROR::2015-04-17 10= =3D :08:11=3D2C953::dispatcher::76::Storage.Dispatcher::(wrapper) {'status': {'= me=3D ssage': "Logical volume does not exist: ('d3ec9e08-1e83-449e-b09d-dd50a4f71= =3D 02f/d0870749-36b0-4ab2-91a5-4743c690551a'=3D2C)"=3D2C 'code': 610}}
Thre= ad-8=3D 87::ERROR::2015-04-17 10:08:11=3D2C975::vm::2331::vm.Vm::(_startUnderlyingV= m)=3D vmId=3D3D`1282c0ed-f753-4484-bb4e-82d41febbba4`::The vm start process fail= ed=3D

Similarly the engine log throws the following error:

2015-04-17 09:39:42=3D2C174 ERROR [org.ovirt.engine.core.dal.dbbroker.audi= tl=3D oghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-94) [4c6a284] C= =3D orrelation ID: null=3D2C Call Stack: null=3D2C Custom Event ID: -1=3D2C Mes= sage: =3D VM testvm is down with error. Exit message: ('Failed to get size for volume= =3D %s'=3D2C 'd0870749-36b0-4ab2-91a5-4743c690551a').
2015-04-17 09:39:42= =3D2C1=3D 75 INFO =3D3B [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (D= ef=3D aultQuartzScheduler_Worker-94) [4c6a284] Running on vds during rerun failed= =3D vm: null
2015-04-17 09:39:42=3D2C177 INFO =3D3B [org.ovirt.engine.c= ore.=3D vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-94) [4c6a284= =3D ] VM testvm (1282c0ed-f753-4484-bb4e-82d41febbba4) is running in db and not= =3D running in VDS node01
2015-04-17 09:39:42=3D2C178 INFO =3D3B [org.o= virt=3D .engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker= =3D -94) [4c6a284] add VM testvm to HA rerun treatment
2015-04-17 09:39:42= =3D =3D2C199 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (Defa= ul=3D tQuartzScheduler_Worker-94) [4c6a284] Rerun vm 1282c0ed-f753-4484-bb4e-82d4= =3D 1febbba4. Called from vds node01

How can I fix this? Do I have t= =3D o edit the database? How can I find which is the correct logical volume ass= =3D ociated with the VM?

Thank you=3D2C

Sokratis
= =3D