Bug 1150242

Summary:	[RFE] Allow removing memory volumes from from the snapshots overview subtab
Product:	[oVirt] ovirt-engine	Reporter:	Allon Mureinik <amureini>
Component:	RFEs	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED WONTFIX	QA Contact:	Avihai <aefrat>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	ahadas, bugs, derez, dfediuck, ebenahar, lsurette, mgoldboi, michal.skrivanek, scohen, srevivo, tnisan
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	rdlugyhe: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	The current release enables removing the memory state from a virtual machine snapshot. This capability is available from the Virtual Machine Snapshots tab. Removing the memory state reduces the amount of storage consumed by the snapshot.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-18 11:33:32 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:	1092447
Bug Blocks:

Description Allon Mureinik 2014-10-07 18:42:30 UTC

Description of problem:
Memory volumes are a non-negligible storage consumer, and are usually less important to keep than disk snapshots (among other reasons, as they will lose their value once one of the disk snapshots from that snapshots is merged).

Comment 1 Sandro Bonazzola 2015-09-04 09:01:38 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 3 Sandro Bonazzola 2019-01-28 09:40:38 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 4 Rolfe Dlugy-Hegwer 2019-02-08 21:30:53 UTC

Please review the updated content in the Doc Text field, above.

Comment 5 Michal Skrivanek 2020-06-23 12:34:44 UTC

This request is not currently committed to 4.4.z, moving it to 4.5

Comment 6 Michal Skrivanek 2021-08-18 11:33:32 UTC

This bug has not been prioritized or updated for a long time and therefore deemed stale. Closing for now, please feel free to update and reopen, but kindly provide justification or development plan how/when to address this bug