Bug 760661

Summary: conflicting terms while uploading catalog entry
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Tomas Sedovic <tsedovic>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, slinaber, 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:17:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
upload_err none

Description wes hayutin 2011-12-06 18:07:25 UTC
Description of problem:

Catalog Entry vs Deployable...

1. Catalog, new catalog entry, upload

Add New Catalog Entry

Choose Option To Upload

    Upload
    From URL

1 error prohibited this record from being saved:

Xml Deployable XML file doesn't resolve valid XML

Catalog: asdf

Comment 1 Tomas Sedovic 2012-01-03 15:46:17 UTC
Patch sent to the list:

https://fedorahosted.org/pipermail/aeolus-devel/2012-January/007808.html

Comment 2 Steve Linabery 2012-01-10 18:17:44 UTC
90826d7818640c3d197033b4d0855f9315bcf1aa in aeolus-conductor-0.8.0-2.el6.src.rpm

Comment 3 Shveta 2012-01-16 12:31:09 UTC
Created attachment 555486 [details]
upload_err

Comment 4 Shveta 2012-01-16 12:32:49 UTC
Added a new deployable with a wrong xml file .

The error message still reads wrong :
"Deployable was not created: Validation failed: seems to be not valid deployable XML: Start tag expected, '<' not found"

=====================================================================
rpm -qa|grep aeolus
aeolus-conductor-0.8.0-5.el6.noarch
aeolus-configure-2.5.0-4.el6.noarch
aeolus-conductor-doc-0.8.0-5.el6.noarch
aeolus-all-0.8.0-5.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
aeolus-conductor-daemons-0.8.0-5.el6.noarch

Comment 5 wes hayutin 2012-01-16 21:04:41 UTC
upload
	
Deployable XML file doesn't resolve valid XML
	
2 errors prohibited this record from being saved:
Name can't be blank
Xml can't be blank

from URL

	
Deployable XML file doesn't resolve valid XML
No URL provided for the deployable XML file.
	
2 errors prohibited this record from being saved:
Name can't be blank
Xml can't be blank

[root@qeblade32 builders]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.8.0-5.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
aeolus-all-0.8.0-5.el6.noarch
aeolus-configure-2.5.0-4.el6.noarch
aeolus-conductor-0.8.0-5.el6.noarch
aeolus-conductor-daemons-0.8.0-5.el6.noarch

Comment 7 errata-xmlrpc 2012-05-15 21:17: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