Bug 1082986 - VM migration back to original host fail on "file exists"
Summary: VM migration back to original host fail on "file exists"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.4.1
Assignee: Vinzenz Feenstra [evilissimo]
QA Contact: Gil Klein
URL:
Whiteboard: virt
Depends On:
Blocks: 1052097
TreeView+ depends on / blocked
 
Reported: 2014-04-01 09:13 UTC by Vinzenz Feenstra [evilissimo]
Modified: 2014-05-08 13:35 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1052097
Environment:
Last Closed: 2014-05-08 13:35:20 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 26278 0 None None None Never
oVirt gerrit 26288 0 None MERGED virt: Remove all guest sockets on cleanup Never
oVirt gerrit 26882 0 None MERGED vm: Fix guest channel symlink creation handling Never
oVirt gerrit 27183 0 None MERGED vm: Fix guest channel symlink creation handling Never

Description Vinzenz Feenstra [evilissimo] 2014-04-01 09:13:05 UTC
+++ This bug was initially created as a clone of Bug #1052097 +++

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):
is30
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

Additional info:
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
    self._waitForIncomingMigrationFinish()
  File "/usr/share/vdsm/vm.py", line 3575, in _waitForIncomingMigrationFinish
    self._domDependentInit()
  File "/usr/share/vdsm/vm.py", line 2926, in _domDependentInit
    self._updateAgentChannels()
  File "/usr/share/vdsm/vm.py", line 2912, in _updateAgentChannels
    os.symlink(path, socketPath)
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

Comment 1 Michal Skrivanek 2014-04-15 16:10:47 UTC
seems there is still an issue with the symlink on vdsm crash&recovery (see bug 1085801)

Comment 2 Michal Skrivanek 2014-04-16 11:07:04 UTC
confirmed an issue - moving back to ASSIGNED, we need to fix it again...

Comment 3 Sandro Bonazzola 2014-05-08 13:35:20 UTC
This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.