Created attachment 562251 [details]
logs

Description of problem:
I created preallocated  disk for VM. While that action I have blocked the connection to the storage. Backed does not rolled back the operation and VM stays in image lock status.

2012-02-15 17:23:30,146 INFO  [org.ovirt.engine.core.bll.storage.RemoveStorageServerConnectionCommand] (QuartzScheduler_Worker-60) Running command: RemoveStorageServerConnectionCommand internal: true. Entities affected :  ID: aaa00000-0000-0000-0000-123456789aaa Type: System
2012-02-15 17:23:30,150 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (QuartzScheduler_Worker-60) START, DisconnectStorageServerVDSCommand(vdsId = 89575b00-50a9-11e1-8b40-001a4a169745, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = NFS, connectionList = [{ id: c0a811d7-49bc-4aa8-a6d8-50bb3e0ce2e8, connection: tiger.qa.lab.tlv.redhat.com:/volumes/tiger1/zeus_ovirt_data_0_nfs_26113247126191 };]), log id: 1fe30c8a
2012-02-15 17:23:30,938 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (QuartzScheduler_Worker-60) FINISH, DisconnectStorageServerVDSCommand, return: {c0a811d7-49bc-4aa8-a6d8-50bb3e0ce2e8=452}, log id: 1fe30c8a
2012-02-15 17:23:30,940 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.MarkPoolInReconstructModeVDSCommand] (QuartzScheduler_Worker-60) START, MarkPoolInReconstructModeVDSCommand(storagePoolId = cd84d709-d762-4df6-9667-a7d0981bd8ed, ignoreFailoverLimit = false, compatabilityVersion = null, reconstructMarkAction = ClearCache), log id: 1008826a
2012-02-15 17:23:30,940 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (QuartzScheduler_Worker-60) clearing cache for problematic entities in pool cd84d709-d762-4df6-9667-a7d0981bd8ed
2012-02-15 17:23:30,940 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.MarkPoolInReconstructModeVDSCommand] (QuartzScheduler_Worker-60) FINISH, MarkPoolInReconstructModeVDSCommand, log id: 1008826a
2012-02-15 17:23:30,954 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (QuartzScheduler_Worker-60) No string for UNASSIGNED type. Use default Log
2012-02-15 17:24:27,659 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (QuartzScheduler_Worker-40) Command SpmStatusVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to SpmStatusVDS, error = Meta Data parameter invalid: ('Version or spm id invalid',)
2012-02-15 17:24:27,660 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (QuartzScheduler_Worker-40) hostFromVds::selectedVds - zeus-vds3.qa.lab.tlv.redhat.com, spmStatus returned null!
2012-02-15 17:25:29,756 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (QuartzScheduler_Worker-75) Command SpmStatusVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to SpmStatusVDS, error = Meta Data parameter invalid: ('Version or spm id invalid',)
2012-02-15 17:25:29,757 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (QuartzScheduler_Worker-75) hostFromVds::selectedVds - zeus-vds3.qa.lab.tlv.redhat.com, spmStatus returned null!
2012-02-15 17:26:31,853 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (QuartzScheduler_Worker-4) Command SpmStatusVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to SpmStatusVDS, error = Meta Data parameter invalid: ('Version or spm id invalid',)







 vdsClient -s 0 getAllTasksStatuses
{'status': {'message': 'OK', 'code': 0}, 'allTasksStatus': {'7dd48e6d-96b3-4b91-9c68-74bcdcd09e3f': {'message': 'Cannot zero out volume', 'code': 374, 'taskID': '7dd48e6d-96b3-4b91-9c68-74bcdcd09e3f', 'taskResult': 'cleanFailure', 'taskState': 'finished'}}}


Version-Release number of selected component (if applicable):
ovirt-engine-backend-3.0.0_0001-1.4.fc16.x86_64

How reproducible:


Steps to Reproduce:
1. Create preallocated disk and block the connection to the storage
2.
3.
  
Actual results:
Backed does not rolled back the operation and VM stays in image lock status.

Expected results:
VM should not stay in lock status

Additional info: