Bug 1235643
| Summary: | RHEV Admin Portal does not show the wipe-after-delete tasks | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Paul Dwyer <pdwyer> | ||||||
| Component: | ovirt-engine | Assignee: | Idan Shaby <ishaby> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Kevin Alon Goldblatt <kgoldbla> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.4.2 | CC: | acanan, amureini, laravot, lsurette, oourfali, ratamir, rbalakri, Rhev-m-bugs, srevivo, tnisan, ykaul, ylavi | ||||||
| Target Milestone: | ovirt-4.2.0 | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-07-16 10:08:13 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1185830 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
Allon, as far as I know you don't have any indication on when this is over. Am I right? Marking as storage for initial investigation, but please move to infra if relevant. IIRC, we do not monitor the WAD task. This was done intentionally, although I do not recall the logic behind this. Liron - could you elaborate please? Allon, yes. When a disk marked as "wipe after delete" is deleted the engine treats the deletion as synchronous - as after the response of the delete call returns the engine, the disk/its storage can't be used anymore (in case of block storage, the lv tag is changed to something like _remve_me before we start to wipe). The basis for this decision is that the purpose of the WAD is to prevent one vm to access that data that was written by other VMs, as till the wipe ends this storage isn't available for other use - it is still prevented while providing faster deletion (the disk won't appear as lock for the whole duration of the wiping). we can improve the tasks tabs appearance on that case. this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high Created attachment 1299267 [details]
Beginning of operation
Created attachment 1299268 [details]
End of operation
I guess that things have changed since this bug was opened. Today, when a disk with WAD enabled is removed, the Tasks bar looks like in "Beginning of operation", and only when the disk is fully wiped and removed (I used a 10G disk, so in my case after almost 3 minutes) it looks like in "End of operation". So it seems like the tasks bar displays a running task until the end of the operation. If that's not what you meant, please reopen. |
Description of problem: Tasks tab shows no active tasks when there is a subtask still running. When removing a disk with Wipe After Delete set, the sub task for the wipe of the disk is still running but tasks show zero tasks running Version-Release number of selected component (if applicable): RHEVM 3.4.2 How reproducible: Customer is easily able to reproduce using steps below Steps to Reproduce: 1. Create a 3,500GB vdisk on a VM ensuring "Wipe After Delete" is enabled. 2. Deactivate the vdisk and remove from the VM. 3. Observe task and subtask appear on the "Tasks" tab. Tasks tab will show "1" to indicate 1 running task (It was at this point I also setup a ps to monitor and report on the dd process on the SPM as it scrubbed the vdisk) 4. After around 50minutes the Tasks tab with indicate "0", but subtask will show an hour glass indicating uncompleted subtask "Deleting Image" (You may have to refresh the Tasks tab view to observe this change to show "0") . Actual results: subtask still running, tasks shows 0 active tasks Expected results: tasks should show task is still running until all subtasks has finished. Additional info: This caused confusion for customer as the vm deletion had finished and tasks showed 0 but the diskspace had not been returned. Expanding the tasks showed the deletion was still happening.