Bug 890331 - vdsm: engine is sending remove volume twice to vdsm when removing a vm (remove VM will fail and cause an inconsistent image state)
Summary: vdsm: engine is sending remove volume twice to vdsm when removing a vm (remov...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Eduardo Warszawski
QA Contact: Dafna Ron
URL:
Whiteboard: storage
Depends On:
Blocks: 890826
TreeView+ depends on / blocked
 
Reported: 2012-12-26 12:53 UTC by Dafna Ron
Modified: 2016-02-10 20:25 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-11 20:16:58 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
logs (1.18 MB, application/x-gzip)
2012-12-26 12:53 UTC, Dafna Ron 		no flags Details
View All

Description Dafna Ron 2012-12-26 12:53:30 UTC 
Created attachment 669218 [details]
logs

Description of problem:

RemoveVMVDSCommand sends delete volume 
RemoveAllVmImagesCommand will send deleteImage which also has delete volume. 


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

si25.2

How reproducible:

100%

Steps to Reproduce:
1. delete a vm 
2.
3.
  
Actual results:

engine sends RemoveVm and DeleteImage - both commands will remove volume in the vdsm 

Expected results:

there is no no need to send delete volume twice

Additional info:
Comment 1 Ayal Baron 2012-12-27 15:02:46 UTC 
I could not find
removeVM in vdsm does not delete the image nor the volume.
In the log I couldn't find any deleteVolume operations called by the engine (nor any call in engine that would support this claim).
Comment 5 Daniel Paikov 2013-03-11 16:24:23 UTC 
Unable to reproduce on latest 3.2.
Note You need to log in before you can comment on or make changes to this bug.