Created attachment 551252 [details]
.

Created attachment 551253 [details]
2

Created attachment 551254 [details]
3

Created attachment 551255 [details]
4

Expected Result: Conductor help convert the spaces into an acceptable character in the auto generated deployable xml

From looking at this a little, it seems that you get here by letting Conductor build a Deployable XML object from an image, where the image name contains spaces.

I *think* that Deltacloud is objecting to spaces in the Assembly name. We could probably just replace with underscores.

Patch sent: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-January/007907.html

Pushed onto master:

commit 521b9b81611ec0c2244064e5bdab5f481f2ed0e3
Author: Matt Wagner <matt.wagner>
Date:   Mon Jan 9 11:02:34 2012 -0500

    Sanitize assembly name to prevent launch errors
    
    Resolves https://bugzilla.redhat.com/show_bug.cgi?id=772322

Created a auto generated deployable with image name containing spaces.

1) Environment -- > New Image .
2) From URL , provide a template 
3) Image name in template contains spaces.
4) Catalog -- > deployable is listed there
5) click on deployable and launch.
6) Image is launched .

Screenshot attached.

Created attachment 552028 [details]
image_with_space

Created attachment 552029 [details]
deployable_with_space

verified in 

rpm -qa|grep aeous
[root@pogolinux-1 yum.repos.d]# rpm -qa|grep aeolus
aeolus-conductor-0.8.0-4.el6.noarch
aeolus-configure-2.5.0-2.el6.noarch
aeolus-conductor-doc-0.8.0-4.el6.noarch
aeolus-all-0.8.0-4.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-4.el6.noarch

bugs in verified or on_qa moving off tracker