Bug 761545

Summary:	view template used in image creation
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Dave Johnson <dajohnso>
Component:	aeolus-conductor	Assignee:	Tomas Sedovic <tsedovic>
Status:	CLOSED ERRATA	QA Contact:	wes hayutin <whayutin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	akarol, deltacloud-maint, ssachdev, tsedovic
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-15 21:28:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dave Johnson 2011-12-08 15:19:44 UTC

Description of problem:
===============================
Sure be nice to be able to view a template xml that a particular image was built from.  Having some issues building templates and forgetting what the image's template was.  Its all stored in iwhd, be nice if we had a link that would show a pretty view of the template without having to fire up ruby irb and see the munged xml.

Comment 1 Tomas Sedovic 2011-12-19 11:43:07 UTC

Fixed in commit: 77014ab62efd1cfcc5c6d9e077c90dae8e7798c9

Comment 2 Shveta 2012-01-04 06:18:55 UTC

Template can be viewed now .
"View template xml " link is added .

Verified in 
rpm -qa|grep aeolus
aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch
rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch
aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch
aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch

Comment 3 wes hayutin 2012-01-12 16:17:24 UTC

bugs in verified or on_qa moving off tracker

Comment 5 errata-xmlrpc 2012-05-15 21:28:30 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.

http://rhn.redhat.com/errata/RHEA-2012-0583.html