<div dir="ltr"><div><div>Confirmed ovirt-3.2 branch of vdsm does work with migrations.<br></div>So there is a difference between it and master as pertains to the migration logic.<br></div>- DHC<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Feb 5, 2013 at 2:26 PM, Dead Horse <span dir="ltr"><<a href="mailto:deadhorseconsulting@gmail.com" target="_blank">deadhorseconsulting@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"><div><div>Dan,<br></div>Building and testing it now.<br></div>- DHC<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 5, 2013 at 2:39 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Mon, Feb 04, 2013 at 10:38:16AM -0600, Dead Horse wrote:<br>
> VDSM built from commit: c343e1833f7b6e5428dd90f14f7807dca1baa0b4 works<br>
> Current VDSM built from master does not work.<br>
><br>
> I could try spending some time trying to bisect and find out where the<br>
> breakage occurred I suppose.<br>
<br>
</div>Would you be kind to find the time to help us here? Clearly, the commit<br>
on top of c343e1833f7b6e5428dd90f14f7807dca1baa0b4 introduces nasty<br>
supervdsm regressions; it has to be reverted for any meaningful testing.<br>
However I do not see how it can be related to the problem at hand.<br>
<br>
Would you at least try out the ovirt-3.2 branch (where the infamous<br>
"zombie reaper" commit is reverted)?<br>
<span><font color="#888888"><br>
Dan.<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>