<div dir="ltr"><div>I just took a look through the vdc_options keys and I only found key entries of "AbortMigrationOnError" for cluster levels 3.0, 3.1, and 3.2 but not 3.3. <br></div><div><br></div>- DHC<br></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 10:55 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 class="im">On Tue, Oct 15, 2013 at 04:42:11PM +0200, Michal Skrivanek wrote:<br>
><br>
> On Oct 15, 2013, at 16:36 , Dead Horse <<a href="mailto:deadhorseconsulting@gmail.com">deadhorseconsulting@gmail.com</a>> wrote:<br>
><br>
> > I have been running EL 6.4 hosts in 3.3 mode for quite some time, I only noticed this breakage in the latest master VDSM 4.13.x. Tagged vdsm versions: ovirt-3.3.0 and ovirt-3.3 do work (if not using master which one of these should be used with 3.3 btw?)<br>
><br>
> it is correct<br>
> I suppose as a workaround you can use engine-config and set AbortMigrationOnError to false for now…<br>
> the default should change to false till EL 6.5 comes out, I guess…<br>
<br>
</div>Global configurable are evil, but yes. Please set it to False by<br>
default, until we can require a libvirt version that has it.<br>
<span class="HOEnZb"><font color="#888888"><br>
Dan.<br>
</font></span></blockquote></div><br></div>