<div dir="ltr">Is the VM showing as locked? You could try to manually unlocking it. I did this in a test environment a while back with some success after a vm was stuck in a "locked" state. Of course the gui and engine should handle most of this for you, manually mucking around the internal DB can cause some pretty serious issues if you are not careful...<div><br></div><div><span id="gmail-docs-internal-guid-5ebb4940-b624-d7ad-e1f7-464f6602a039"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">sudo su postgres</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">psql -d engine -U postgres </span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">SELECT vm_guid, vm_name FROM vm_static WHERE vm_name='<b>VM_Name_Here</b>';</span></p><div><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">This should return a string such as: "</span><span style="background-color:transparent;color:rgb(0,0,0);font-family:Arial;font-size:11pt;font-weight:700;white-space:pre-wrap">0ec20854-e1ca-4e49-be87-a6cd36d40c18"</span></div><div><span style="background-color:transparent;color:rgb(0,0,0);font-family:Arial;font-size:11pt;font-weight:700;white-space:pre-wrap"><br></span></div><div><span style="background-color:transparent;color:rgb(0,0,0);font-family:Arial;font-size:11pt;font-weight:700;white-space:pre-wrap">Reset the lock:</span></div><div><span id="gmail-docs-internal-guid-5ebb4940-b625-b889-54b8-79b3e092d57b"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">update vm_dynamic SET status=0 where vm_guid='<span style="font-size:14.6667px;font-weight:bold">0ec20854-e1ca-4e49-be87-a6cd36d40c18</span>';</span></span><span style="background-color:transparent;color:rgb(0,0,0);font-family:Arial;font-size:11pt;font-weight:700;white-space:pre-wrap"><br></span></div><div><br></div><div><br></div></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 13, 2017 at 11:01 AM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>it seems the same lock (with the same date) has come again in the list of tasks.</div><div>Now I have two things in "supposed running" tasks:</div><div>- the "Restoring VM Snapshot Active VM before the preview of VM snaptest" of 8/11</div><div>- the "Creating VM Snapshot 13-11-2017-16-30-Danilo for VM apex" (now running since half an hour for a vm that has only one 90Gb disk on SAN FC storage domain)</div><div><br></div><div>It was not me to run the "create snapshot" command today, so I'm not sure if it was the snapshot creation job responsible of letting come out again the former hung task... or if it was already there before...</div><div>Any further hint?</div><div>How can I manually verify the status of the snapshot creation task?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Gianluca</div><div><br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 10, 2017 at 5:01 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><div class="gmail_extra"><div class="gmail_quote">On Fri, Nov 10, 2017 at 3:48 PM, <span dir="ltr"><<a href="mailto:nicolas@devels.es" target="_blank">nicolas@devels.es</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
</blockquote>
<br></span>
I've seen this behavior too. IIRC the stale cleaning was not instant, it took some time to be applied.<br>
<br>
Regards.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Gianluca<br>
</blockquote>
</blockquote></div><br></div></span><div class="gmail_extra">Confirmed.</div><div class="gmail_extra">Quite soon after the command I saw that the status of the "Current" snapshot line changed from Locked (it was so since 8/11) to OK, but the task remained at least for half an hour.</div><div class="gmail_extra">Now, after about one hour and a half I connected again to the web admin gui and I see 0 Tasks, so the problem has been resolved.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks again,</div><div class="gmail_extra">Gianluca </div><div class="gmail_extra"><br></div></div>
</blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>