Bug 1483584 - VM hibernation memory disks description is empty
Summary: VM hibernation memory disks description is empty
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Tal Nisan
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-21 12:45 UTC by Tal Nisan
Modified: 2017-12-20 10:56 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 10:56:34 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81154 0 master MERGED core: Set hibernation disks description correctly 2017-08-29 13:21:46 UTC

Description Tal Nisan 2017-08-21 12:45:16 UTC 
Description of problem:
VM hibernation memory disks description should be "memory dump/metadata for VM hibernation" but when hibernating a VM the description is empty

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


How reproducible:
100%

Steps to Reproduce:
1. Hibernate a VM
2. Locate the memory metadata/dump disks and check the description
3.

Actual results:
The description is empty

Expected results:
The description should be informative

Additional info:
Comment 1 Raz Tamir 2017-09-04 16:03:35 UTC 
The memory disk alias is:
"golden_env_mixed_virtio_1_0_hibernation_memory"
The description is:
"memory dump for VM hibernation"

Verified on ovirt-engine-4.2.0-0.0.master.20170903205106.gitb17261a.el7.centos
Comment 2 Sandro Bonazzola 2017-12-20 10:56:34 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.
Note You need to log in before you can comment on or make changes to this bug.