Bug 967602 - vdsm: we fail to destroy vm that was paused on EIO with "Drive is not a vdsm image"
vdsm: we fail to destroy vm that was paused on EIO with "Drive is not a vdsm ...
Status: CLOSED DUPLICATE of bug 980054
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: 3.3.0
Assigned To: Nobody's working on this, feel free to take it
Dafna Ron
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-05-27 10:23 EDT by Dafna Ron
Modified: 2016-02-10 13:41 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-16 10:16:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
logs (1.56 MB, application/x-gzip)
2013-05-27 10:23 EDT, Dafna Ron
no flags Details

  None (edit)
Description Dafna Ron 2013-05-27 10:23:49 EDT
Created attachment 753644 [details]

Description of problem:

I live storage migrated a vm disk and blocked connectivity to the storage from the hsm only (host that the vm was running on). 
when the vm paused I tried to destroy it and failed in vdsm with Drive is not a vdsm image followed by: 

m volExtensionChunk:1024 watermarkLimit:536870912
Traceback (most recent call last):
  File "/usr/share/vdsm/clientIF.py", line 334, in teardownVolumePath
    res = self.irs.teardownImage(drive['domainID'],
  File "/usr/share/vdsm/libvirtvm.py", line 1071, in __getitem__
    raise KeyError(key)
KeyError: 'domainID'

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. in iscsi storage with two hosts and two domains create a vm from template and run it on the hsm
2. LSM the vm disk 
3. block connectivity to the storage in hsm only when engine logs "SyncImageGroupDataVDSCommand" 
4. when the vm pauses try to destroy it (power off)

Actual results:

we fail to destroy the vm with no alert in UI. 

Expected results:

we should be able to destroy the vm

Additional info: logs
Comment 1 Ayal Baron 2013-07-10 04:44:43 EDT
Fede, is this solved already?
Comment 2 Ayal Baron 2013-07-16 10:16:49 EDT

*** This bug has been marked as a duplicate of bug 980054 ***

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