Description of problem:
On rhevm 3.3 (is30), Have 2 3.3 hosts in 3.2 cluster.
Downgrade vdsm of host1 (remove the 3.3 vdsm, and install 3.2 vdsm).
Run a VM on host1.
Migrate the VM to host2.
Upgrade host1 vdsm to 3.3.
Migrate VM back to original host, host1
Migration failed on "file exists" error.
Version-Release number of selected component (if applicable):
vdsm 3.3: (is30 ) vdsm-4.13.2-0.5.el6ev.x86_64.rpm
vdsm 3.2: (sf22.4) vdsm-4.10.2-30.1.el6ev.x86_64.rpm
event error on rhevm: VM mig_ver is down. Exit message: [Errno 17] File exists.
vdsm error on destination host (host1):
Thread-38::ERROR::2014-01-12 16:21:09,752::vm::2162::vm.Vm::(_startUnderlyingVm) vmId=`53396dbd-388f-47be-a936-4a92a5dc6a6a`::The vm start process failed
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 2140, in _startUnderlyingVm
File "/usr/share/vdsm/vm.py", line 3575, in _waitForIncomingMigrationFinish
File "/usr/share/vdsm/vm.py", line 2926, in _domDependentInit
File "/usr/share/vdsm/vm.py", line 2912, in _updateAgentChannels
OSError: [Errno 17] File exists
Thread-38::DEBUG::2014-01-12 16:21:09,766::vm::2615::vm.Vm::(setDownStatus) vmId=`53396dbd-388f-47be-a936-4a92a5dc6a6a`::Changed state to Down: [Errno 17] File exists
Created attachment 849248 [details]
engine.log migration start & fail @ 2014-Jan-12, 16:21
Created attachment 849249 [details]
Created attachment 849250 [details]
not sure if 3.3.z needed, let's review
*** Bug 1052841 has been marked as a duplicate of this bug. ***
Merged to u/s master as http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=commit;h=4a7af0277aa441478b040163190ded27a9d7dcc2
Merged u/s to ovirt-3.4 branch as http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=commit;h=be6302a938c1a1f1dac1e03b65ce10c7fecceb92
discovered an issue described in bug 1085801. We need an additional fix and possibly a backport to 3.3 as more and more people are hitting this
*** Bug 1085801 has been marked as a duplicate of this bug. ***
Verified on rhevm3.4 av8.1:
Had 3.2 cluster.
host_1 3.3 vdsm vdsm-4.13.2-0.14.el6ev (from is36)
host_2 3.4 vdsm vdsm-4.14.7-0.2.rc.el6ev.x86_64
Run a VM on host_1
Migrate VM to host_2
Upgrade vdsm on host_1 from 3.3 to 3.4
Migrate VM back to host_1
NO migration failures.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.