DescriptionJaroslav Spanko
2016-12-21 16:13:46 UTC
Description of problem:
Live migration of disks with high I/O (Mysql,Nagios,hosting services) failed.
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 372, in wrapper
return f(*a, **kw)
File "/usr/share/vdsm/virt/vm.py", line 4924, in run
self.tryPivot()
File "/usr/share/vdsm/virt/vm.py", line 4893, in tryPivot
ret = self.vm._dom.blockJobAbort(self.drive.name, flags)
File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 69, in f
ret = attr(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 123, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 917, in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 733, in blockJobAbort
if ret == -1: raise libvirtError ('virDomainBlockJobAbort() failed', dom=self)
ckJobAbort
libvirtError: block copy still active: disk 'vda' not ready for pivot yet
Version-Release number of selected component (if applicable):
vdsm-4.18.13-1
libvirt-client-1.2.17-13
rhevm-4.0.5.5-0.1
How reproducible:
Don't know, this happened every time on the same VM with the high disk load
Steps to Reproduce:
1. Live migrate disk from one Storage domain to another
2. After some minutes migration fail
3.
Actual results:
Live migration of disk with high load failed with block copy still active
Expected results:
Using libvirt async events instead of calling self._dom.blockJobInfo every time
Additional info:
Most probably hitting https://bugzilla.redhat.com/show_bug.cgi?id=1382165
Description of problem: Live migration of disks with high I/O (Mysql,Nagios,hosting services) failed. File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 372, in wrapper return f(*a, **kw) File "/usr/share/vdsm/virt/vm.py", line 4924, in run self.tryPivot() File "/usr/share/vdsm/virt/vm.py", line 4893, in tryPivot ret = self.vm._dom.blockJobAbort(self.drive.name, flags) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 69, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 123, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 917, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 733, in blockJobAbort if ret == -1: raise libvirtError ('virDomainBlockJobAbort() failed', dom=self) ckJobAbort libvirtError: block copy still active: disk 'vda' not ready for pivot yet Version-Release number of selected component (if applicable): vdsm-4.18.13-1 libvirt-client-1.2.17-13 rhevm-4.0.5.5-0.1 How reproducible: Don't know, this happened every time on the same VM with the high disk load Steps to Reproduce: 1. Live migrate disk from one Storage domain to another 2. After some minutes migration fail 3. Actual results: Live migration of disk with high load failed with block copy still active Expected results: Using libvirt async events instead of calling self._dom.blockJobInfo every time Additional info: Most probably hitting https://bugzilla.redhat.com/show_bug.cgi?id=1382165