<div dir="ltr"><div><div>This happened when I tried to switch the SD "mi-ci-3" to maintenance mode while copying template's disk image from "mi-ci-1" to "mi-ci-5" (and "mi-ci-3" also had this image already copied). I have already fixed this by some changes in DB and destroy SD. My installation is not self-hosted deploy.<br></div><br></div>I'll try to dig logs from that situation today and post it here (I produce really a loot of logs)...<br><div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-04-13 17:45 GMT+02:00 Bob Doolittle <span dir="ltr"><<a href="mailto:bob@doolittle.us.com" target="_blank">bob@doolittle.us.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Are you using a self-hosted deployment? If so, this may be the issue that's been reported for almost a year now that results in an inability to shutdown cleanly due to sanlock leases being held which result in watchdog timeouts that cause a system to reboot instead of shutdown. See for example: <a href="http://lists.ovirt.org/pipermail/users/2014-May/024652.html" target="_blank">http://lists.ovirt.org/pipermail/users/2014-May/024652.html</a><br><br></div>I still experience this with 3.5.1. When I poweroff my machine I have to physically be there to hit the power switch when it tries to reboot after the wdmd watchdog timeout. I notice during shutdown that the storage domains fail to unmount.<span><font color="#888888"><br><br></font></span></div><span><font color="#888888">-Bob<br></font></span></div>
</blockquote></div><br></div></div>