Bug 1026995 - [RFE] Snapshot deletion does not show progress
Summary: [RFE] Snapshot deletion does not show progress
Keywords:
Status: CLOSED DUPLICATE of bug 529086
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ovirt-4.0.0-alpha
: ---
Assignee: Scott Herold
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On: 910729 1080372
Blocks: 529086
TreeView+ depends on / blocked
 
Reported: 2013-11-05 20:15 UTC by Peter Manzella
Modified: 2023-12-15 15:46 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-27 11:26:44 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
sherold: Triaged+
lsvaty: testing_plan_complete-


Attachments (Terms of Use)

Description Peter Manzella 2013-11-05 20:15:30 UTC
Description of problem: Deleting a snapshot does not have any indication of progress. For example, deleting a snapshot of a 2TB disk may take 24+ hours to complete without any indication of status.


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1.Create a snapshot for a virtual machine guest.
2.Delete the snapshot.
3.There is no indication of the progress until the delete finishes.

Actual results: No progress indicator


Expected results: Indication of relative progress.


Additional info: Although there are single RFEs requesting progress indicators on numerous operations, it would appear that an RFE for each discrete progress indicator might more closely map to the development process.

Comment 2 Robert McSwain 2014-10-11 15:18:42 UTC
Any chance of this being picked up for 3.5 or 3.6? This is still a highly sought after request from customers. Thanks!

Comment 3 Allon Mureinik 2014-11-30 17:10:50 UTC
The new task system planned for 3.6 may enable this. On our radar.

Comment 7 Yaniv Lavi 2016-01-27 11:26:44 UTC

*** This bug has been marked as a duplicate of bug 529086 ***


Note You need to log in before you can comment on or make changes to this bug.