Bug 1624857 - [RFE] Snapshot memory and metadata disks names are not distinguishable
Summary: [RFE] Snapshot memory and metadata disks names are not distinguishable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.2.6.2
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.0
: ---
Assignee: Tal Nisan
QA Contact: Evelina Shames
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-03 12:49 UTC by Elad
Modified: 2019-02-13 07:42 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.3.0_rc
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-13 07:42:57 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.3?
rule-engine: planning_ack?
rule-engine: devel_ack+
ebenahar: testing_ack+

Attachments (Terms of Use)
screenshot (59.03 KB, image/png)
2018-09-03 12:49 UTC, Elad 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 95606 0 master MERGED core: Put VM name in generated memory disks alias 2018-11-22 12:28:01 UTC

Description Elad 2018-09-03 12:49:18 UTC 
Created attachment 1480542 [details]
screenshot

Description of problem:

'snapshot_memory' and 'snapshot_metadata' disks names don't have any indication to which snapshot and VM they belong to.
In case there are a lot of them, disks tab/collection is filled with these disk names, which don't really mean anything and they flood the view. 
See attached screenshot
Comment 1 Michal Skrivanek 2018-09-04 13:26:12 UTC 
This is about the Disks view so moving to Storage for consideration
Comment 2 Evelina Shames 2019-01-30 15:21:28 UTC 
Verified on Engine 4.3.0-0.5
Comment 3 Sandro Bonazzola 2019-02-13 07:42:57 UTC 
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.