Bug 1123643
| Summary: | [RFE] Allow user to follow block disks removal operation in case "wipe after delete flag" is marked | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Ori Gofen <ogofen> |
| Component: | RFEs | Assignee: | Nobody <nobody> |
| Status: | CLOSED WONTFIX | QA Contact: | Raz Tamir <ratamir> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.0 | CC: | acanan, alitke, bugs, dfediuck, fsimonce, lpeer, lsurette, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi |
| Target Milestone: | --- | Keywords: | FutureFeature, Improvement |
| Target Release: | --- | Flags: | ylavi:
ovirt-future?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-21 09:26:50 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: | |||
What's probably needed here is some sort of introspection into VDSM's garbage collection mechanism, once one is introduced (post SPM removal). Currently we report the total space and free space. We could add another figure (eg. Total Garbage or Reclaimable) to report in the storage domain details. This figure could be calculated and updated by engine without any vdsm intervention. Closing old RFEs. If relevant please re-open and explain why. |
Description of problem: Right now when creating a large block disk (the larger the disk,the larger the problem) and marking "wipe after delete" flag as 'True',then removing this disk. disk existence is wiped from the UI while actually,removing this kind of disk takes a lot of time(since vdsm has to fill the whole disk with zero's). this can be very misleading to an unaware sysadmin. for example: Deleting two 30G disks(wipe_after_delete='True') on iscsi took almost 25 minutes async task table reported this two assignment as being executed engine=# SELECT step_id,action_type,task_params_class from async_tasks; step_id | action_type | task_params_class --------------------------------------+-------------+----------------------------------------------------------- e7c89068-df9d-4ff4-ac63-8d6e6d9bed98 | 230 | org.ovirt.engine.core.common.action.RemoveImageParameters c961cc72-ae3d-4d03-9463-6750e28f8228 | 230 | org.ovirt.engine.core.common.action.RemoveImageParameters (2 rows) lv's were activated and writable 6c65483f-5316-474a-b04b-4cb397a8a870 db7d2a45-45e7-457c-b40f-47670dda811d -wi-ao---- 30.00g 7c163ea3-fe24-435f-a9e1-dcfe9093d2c0 db7d2a45-45e7-457c-b40f-47670dda811d -wi-ao---- 30.00g and during all this time (25 minuts),UI reported on an unused ISCSI domain(with no disks or vm's on it) with 1G free space(out of 65G) RFE is needed to help user follow the process of deleting this kind of disk Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: