Description of problem: I did a Preview snapshot of a VM and the action failed. The disk in question remained in "Image locked" state not just after the job/task was declared failed, but even after it was deleted from vdsm jobs and also from engine jobs. It also took quite a long time before the jobs were deleted from vdsm and engine (but they eventually were purged so this is good). The disk status should be changed to Active right after the job is no longer active instead. Version-Release number of selected component (if applicable): is19-is20.1 How reproducible: the task failure that triggered the bug occurred just once Steps to Reproduce: 1. make some async task on disk fail 2. 3. Actual results: the disk remains in "image locked" state forever Expected results: the disk status is cleared right after the job terminates in any way Additional info:
Created attachment 818297 [details] engine logs
just to be clear on jobs: bot "vdsClient -s 0 getAllTasks{Statuses,Info}" and GET /api/jobs show empty result...
can u provide steps how to reproduce/verify this?
I'd like to select a different approach for solving this bug. moving it back to assigned. I will provide steps once the bug gets back to you Thanks
Is the fix supposed to release the "image locked" status of a disk that already got to the state or is it supposed just to prevent reaching such a condition?
(In reply to David Jaša from comment #9) > Is the fix supposed to release the "image locked" status of a disk that > already got to the state or is it supposed just to prevent reaching such a > condition? preventing. (In reply to Lukas Svaty from comment #7) > can u provide steps how to reproduce/verify this? Add a quota to a disk, and create a snapshot. move the DC to disabled quota mode, and remove the quota. now try to preview the snapshot.
tested on is25
Closing - RHEV 3.3 Released