Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1483500

Summary: Show the relevant VM info in memory disks description
Product: [oVirt] ovirt-engine Reporter: Tal Nisan <tnisan>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: amureini, bugs
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:53:52 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:
Attachments:
Description Flags
The current view of the disks none

Description Tal Nisan 2017-08-21 09:31:41 UTC
Description of problem:
Memory disks are displayed in the UI & REST but without any indication to which VM and snapshot they belong to, when creating a snapshot with memory disks those disks should be created with an indication in their description to which VM they belong and which snapshot

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


How reproducible:
100%

Steps to Reproduce:
1. Create a live snapshot of a VM containing memory
2. Find the memory disks in the Disks main tab
3.

Actual results:
The memory disks do not contain a description, just a generic alias

Expected results:
The memory disks description should contain information on which VM and snapshot they belong to

Additional info:

Comment 1 Tal Nisan 2017-08-21 10:10:09 UTC
Created attachment 1316169 [details]
The current view of the disks

Comment 2 Raz Tamir 2017-09-04 15:59:47 UTC
The description of the memory disk is:
"Memory snapshot disk for snapshot 'snap' of VM 'golden_env_mixed_virtio_1_0' (VM ID: 'df70f7ae-3071-4bc3-956d-ecfee93385ad')"

Verified on ovirt-engine-4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos

Comment 3 Sandro Bonazzola 2017-12-20 10:53:52 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.