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

Bug 1483584

Summary:	VM hibernation memory disks description is empty
Product:	[oVirt] ovirt-engine	Reporter:	Tal Nisan <tnisan>
Component:	BLL.Storage	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Raz Tamir <ratamir>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	future	CC:	amureini, bugs, ratamir
Target Milestone:	ovirt-4.2.0	Flags:	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:56:34 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:

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.