I was in the process of upgrading from 3.5.5 to 3.6.4 when it happened. I a= =3D m sure there were version mismatches.

I think what generated this issue was that I edited the cluster the host be= =3D longed to while it was going down for maintenance. This caused the tasks ta= =3D b to show multiple tasks of the host going down for maintenance. They all e= =3D ventually went into en error state and the task kept repeating itself until I rebooted the host.

Andrew Wippler | Sr. Systems Administrator | Lancaster Baptist Church | Dr.= =3D Paul Chappell, Pastor

From: Michal Skrivane= k &l=3D t;michal.skrivanek(a)redhat.com>
Sent: Friday, April 01, 2016 1:00 AM
To: Andrew Wippler
Cc: users(a)ovirt.org
Subject: Re: [ovirt-users] Several VM's stuck in Migration

On 31 Mar 2016, at 19:48, Andrew Wippler <Andrew.Wippler(a)la= ncaste=3D rbaptist.org> wrote:

Mark,

Hopefully you have resolved your stuck VM issue by now (n= ea=3D rly two months later). I came across this email from a google search. I was= =3D having the same exact problem with VMs being stuck in migration mode. The = =3D trigger to the VM migration issue was that I was setting my Host into maintenance mode. It migrated half of = =3D the active VMs successfully and the other half were stuck.

Hi,

It would be great to get logs from the system, or at least describe the spe= =3D cifics (anything special? gluster? old version?)

otherwise no one will ever be able to help;)

Thanks,

michal

There were two things I had to do to fix all of my stuck = VM=3D s:

1. I shut down the host (long enough for oVirt to fence i= t =3D and notice that it was down). I then powered it on and "confirmed host= =3D as rebooted." This reset the active VM count on the host and turned o= =3D n my HA VMs on other hosts.

2. For the one VM that was still stuck after a host reboo= t,=3D I had to login to postgres and set the status to 0 on that VM. This allowe= =3D d me to shut down the migrating VM and start it back up. (I do not think I = =3D would have had to do this step if I did not alter the database entry for this VM before rebooting the host.)= =3D

For step 2, I used the methods described here: https://ac= cess=3D .redhat.com/discussions/688043 and as seen below:

ssh ovirt-engine

su postgres

psql

\connect engine

SELECT vm_guid status FROM vm_static WHERE vm_name=3D3D'X= XXX'=3D ;

UPDATE vm_dynamic SET status=3D3D0 WHERE vm_guid=3D3D'xxx= xxxxx'=3D ;

UPDATE vm_dynamic SET run_on_vds =3D3D null WHERE v= m_gu=3D id=3D3D'xxxxxxxx';

\q

(I was then able to shut down the VM)

--
Andrew Wippler <andrew.wippler(a)lancasterba= ptist.=3D org> | Sr. Systems Administrator | Lancaster Baptist Church

_______________________________________________
Users mailing list
Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users