Description of problem: Images which are not able to be marked as deleted in the storage by VDSM should be marked as Illegal in the engine DB, so user will be able to delete them again. un-succeeded deletion can be on move operation (When the original copy is deleted at the end of the process) also at create VM from template or create template which fails. import VM which fails and so on. The purpose of this RFE is to solve an issue when images will be blocked from being removed since other shared volumes still hasn't been removed from the storage (for example a template which has based VM images related to it). To prevent a scenario, which those images are no longer in the DB, we should leave those images in the DB until they are marked as removed in the storage. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Images which are not able to be marked as removed from the storage by VDSM should be marked as Illegal in the engine DB, so user will be able to delete them again. Additional info:
*** Bug 965936 has been marked as a duplicate of this bug. ***
Link to the wiki : http://www.ovirt.org/Features/Move_Disk_Two_Phase_Commit
Sergey, this sounds like something you're already working on?
I'll take it with Maor, I think its already resolved in 3.3.
(In reply to Sergey Gotliv from comment #4) > I'll take it with Maor, I think its already resolved in 3.3. So was it?
Currently we mark those disks with ILLEGAL only on delete, but we still don't support the move operation (which deletes the image from the source domain). The fix for that should also be taken care of with this bug https://bugzilla.redhat.com/960169
Liron - is this even relevant nowadays?
Allon, yes. Once BZ 960169 will be solved, we'll be able to leave the db record for the disk on the source domain in ILLEGAL status which will let the user to attempt to delete it. As today we support only one copy for a regular disk - there's an audit log indicating that there are leftovers on the storage but you can't clean it using the engine. BZ 1416113 is also a duplicate of this bug.
*** Bug 1416113 has been marked as a duplicate of this bug. ***
Closing old RFEs, please reopen if still relevant.
BZ<2>Jira Resync