Description of problem:
Stop VM fails through REST API because of Cannot remove Fs that does not exists in: /var/run/vdsm/payload
Version-Release number of selected component (if applicable):
vt5
How reproducible:
not sure
heppend once in MultiVM teardown of run
http://jenkins.qa.lab.tlv.redhat.com:8080/view/Compute/view/3.5-git/view/Dashboard/job/3.5-git-compute-sla_ha_reservation/28/
Steps to Reproduce:
1. created 8 VMs
2. Start them
3. Move one host to maintenance
4. try to stop 1 VM
Actual results:
Stop operation failed.
Additional info:
Adding logs from machine running VMs (.39), other host and engine
supervdsm.log:
MainProcess|Thread-2906::DEBUG::2014-10-14 13:53:54,717::supervdsmServer::101::SuperVdsm.ServerCallback::(wrapper) call removeFs with ('',) {}
MainProcess|Thread-2906::ERROR::2014-10-14 13:53:54,717::supervdsmServer::105::SuperVdsm.ServerCallback::(wrapper) Error in removeFs
Traceback (most recent call last):
File "/usr/share/vdsm/supervdsmServer", line 103, in wrapper
res = func(*args, **kwargs)
File "/usr/share/vdsm/supervdsmServer", line 360, in removeFs
return mkimage.removeFs(path)
File "/usr/share/vdsm/mkimage.py", line 143, in removeFs
_P_PAYLOAD_IMAGES)
Exception: Cannot remove Fs that does not exists in: /var/run/vdsm/payload
(In reply to Omer Frenkel from comment #2)
> Francesco, maybe related to the cd device disappearing in migration? ( bug
> 1145636 )
I definitely think so. I observed thus very same behaviour on the affected box. Let's close this as duplicate of bz1145636, and reopen if new evidence comes out.
*** This bug has been marked as a duplicate of bug 1145636 ***