Bug 766993 - no xml validation on deployable xml
Summary: no xml validation on deployable xml
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Jan Provaznik
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-12 22:41 UTC by Dave Johnson
Modified: 2012-05-15 21:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 21:28:54 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Dave Johnson 2011-12-12 22:41:03 UTC 
Description of problem:
================================
I noticed that the deployable xml from a catalog entry is not validated for closing elements.  This xml should? (at least, could) go through the same general xml validator that is being used for the template xml.

Uploading a good deployable xml and removing the closing image element, saves successfully.  Would think we would want to validate that xml instead of letting the actual deploy error out on it.
Comment 2 Jan Provaznik 2012-01-02 09:25:18 UTC 
fixed in commit d7d7a295ad5b774103dbaebdb820d9ea49ad066f
Comment 3 Steve Linabery 2012-01-10 18:12:18 UTC 
d7d7a295ad5b774103dbaebdb820d9ea49ad066f in aeolus-conductor-0.8.0-2.el6.src.rpm
Comment 4 Dave Johnson 2012-01-11 21:25:43 UTC 
good 2 go in aeolus-conductor-doc-0.8.0-5.el6.noarch
Comment 5 wes hayutin 2012-01-12 16:16:50 UTC 
bugs in verified or on_qa moving off tracker
Comment 7 errata-xmlrpc 2012-05-15 21:28:54 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
Note You need to log in before you can comment on or make changes to this bug.