On Oct 12, 2013, at 00:30 , Dan Kenigsberg <danken@redhat.com> wrote:
On Fri, Oct 11, 2013 at 03:30:35PM -0500, Dead Horse wrote:
VM migrations are failing with latest master engine and vdsm
logs attached from engine and both hosts
Hosts are EL 6.4 with latest master VDSM
Thanks for your report!
Thread-195::ERROR::2013-10-11 15:22:39,508::vm::304::vm.Vm::(run) vmId=`4bad94ad-c338-4ec5-8e5b-9910d58c1854`::Failed to migrate Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 291, in run self._startUnderlyingMigration() File "/usr/share/vdsm/vm.py", line 369, in _startUnderlyingMigration self._abortOnError else 0), AttributeError: 'module' object has no attribute 'VIR_MIGRATE_ABORT_ON_ERROR'
Peter, Michal, I think that VIR_MIGRATE_ABORT_ON_ERROR is expected only in el6.5, which is still not public Bug 972675 - Fail migration when VM get paused due to EIO
This must be reverted in vdsm or hacked in Engine (do not set abortOnError=True if libvirt < libvirt-0.10.2-20.el6)
as of http://gerrit.ovirt.org/#/c/19312/ the flag is sent for 3.3 clusters, which is correct I thought you're not supposed to have EL 6.4 host in 3.3 cluster. 6.5 should work.. Thanks, michal
Additionally the hosts seem to lose connection with their storage domains (new behavior), are offline then recovered (even though not is physically wrong).