<div dir="ltr">Please provide logs for the SPM and engine.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre cols="72"><span style="font-family:arial,helvetica,sans-serif">Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: <a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>
IRC : ydary</span></pre>
</div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Jan 5, 2017 at 9:07 PM, Robert Story <span dir="ltr"><<a href="mailto:rstory@tislabs.com" target="_blank">rstory@tislabs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, 5 Jan 2017 14:35:33 +0000 Clint wrote:<br>
CB> I'm having trouble with a VM showing that the disk is locked after<br>
CB> trying to clone that VM to a new VM. The source machine was powered off<br>
CB> when the clone was initiated. The source and destination disks both<br>
CB> show to be locked and are currently un-usable. This situation was<br>
CB> brought on around December 27 2016 and persists.<br>
<br>
I have the exact same issue, except I'm running 4.0.5.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
Robert<br>
<br>
--<br>
Senior Software Engineer @ Parsons<br>
</font></span><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>