Bug 1013670

Summary:	New Template: comment is not saved when creating new template
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Pavel Novotny <pnovotny>
Component:	ovirt-engine-webadmin-portal	Assignee:	Martin Betak <mbetak>
Status:	CLOSED ERRATA	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	ecohen, iheim, juwu, lsvaty, michal.skrivanek, rbalakri, Rhev-m-bugs, sherold, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	ovirt-3.5.0-alpha1	Doc Type:	Bug Fix
Doc Text:	Previously, the comment field was not set up properly for creating a template from a virtual machine so comments were not saved. With this update, the comment field is properly saved when creating a template from a virtual machine.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-11 17:55:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	610501
Bug Blocks:	1142923, 1156165

Description Pavel Novotny 2013-09-30 14:55:37 UTC

Description of problem:
Comment is not saved when creating new template.

Version-Release number of selected component (if applicable):
rhevm-3.3.0-0.23.master.el6ev.noarch (is16)

How reproducible:
100%

Steps to Reproduce:
1. Have a VM to create a template from.
2. Select the VM, click on `Make Template` button, enter template name *and a comment*; submit.
3. Go to the Templates tab.

Actual results:
The Comment column of the new template is empty (as is the Comment field in the Edit Template dialog).

Expected results:
The Comment value entered in the New Template dialog should be saved.

Additional info:

Comment can be set only via editing template.

Comment 3 Lukas Svaty 2014-08-04 09:21:36 UTC

verified in ovirt-3.5.0-beta2

Comment 5 errata-xmlrpc 2015-02-11 17:55:16 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://rhn.redhat.com/errata/RHSA-2015-0158.html