<div dir="ltr"><div><div>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: <a class="" href="http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=shortlog;h=refs/heads/ovirt-3.3.0" style="color:rgb(0,0,0);text-decoration:none;font-weight:bold;font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(237,236,230)">ovirt-3.3.0</a> and <a class="" href="http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=shortlog;h=refs/heads/ovirt-3.3" style="color:rgb(0,0,0);text-decoration:none;font-weight:bold;font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(246,246,240)">ovirt-3.3</a> do work (if not using master which one of these should be used with 3.3 btw?)<br>
</div>The running version of libvirt on the hosts is: libvirt-0.10.2-18.0.1.el6_4.14.x86_64<br>
</div><div><br></div>- DHC<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 9:05 AM, Michal Skrivanek <span dir="ltr"><<a href="mailto:mskrivan@redhat.com" target="_blank">mskrivan@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"><br>
On Oct 12, 2013, at 00:30 , Dan Kenigsberg <<a href="mailto:danken@redhat.com">danken@redhat.com</a>> wrote:<br>
<br>
> On Fri, Oct 11, 2013 at 03:30:35PM -0500, Dead Horse wrote:<br>
>> VM migrations are failing with latest master engine and vdsm<br>
>><br>
>> logs attached from engine and both hosts<br>
>><br>
>> Hosts are EL 6.4 with latest master VDSM<br>
><br>
> Thanks for your report!<br>
><br>
> Thread-195::ERROR::2013-10-11 15:22:39,508::vm::304::vm.Vm::(run) vmId=`4bad94ad-c338-4ec5-8e5b-9910d58c1854`::Failed to migrate<br>
> Traceback (most recent call last):<br>
> File "/usr/share/vdsm/vm.py", line 291, in run<br>
> self._startUnderlyingMigration()<br>
> File "/usr/share/vdsm/vm.py", line 369, in _startUnderlyingMigration<br>
> self._abortOnError else 0),<br>
> AttributeError: 'module' object has no attribute 'VIR_MIGRATE_ABORT_ON_ERROR'<br>
><br>
><br>
> Peter, Michal, I think that VIR_MIGRATE_ABORT_ON_ERROR is expected only in<br>
> el6.5, which is still not public<br>
> Bug 972675 - Fail migration when VM get paused due to EIO<br>
><br>
> This must be reverted in vdsm or hacked in Engine (do not set abortOnError=True if libvirt < libvirt-0.10.2-20.el6)<br>
<br>
</div>as of <a href="http://gerrit.ovirt.org/#/c/19312/" target="_blank">http://gerrit.ovirt.org/#/c/19312/</a> the flag is sent for 3.3 clusters, which is correct<br>
I thought you're not supposed to have EL 6.4 host in 3.3 cluster. 6.5 should work..<br>
<br>
Thanks,<br>
michal<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
>><br>
>> Additionally the hosts seem to lose connection with their storage domains<br>
>> (new behavior), are offline then recovered (even though not is physically<br>
>> wrong).<br>
><br>
<br>
</div></div></blockquote></div><br></div>