Hide Forgot
Description of problem: https://hp-sl2x170zg6-01.rhts.eng.bos.redhat.com/conductor/catalogs/2/deployables/7 You can see its difficult to parse the Target Image UUID's Component Outline UUID: %{uuid} ce5fba7b-d5d9-4951-af93-ba5c4e8e6814 Latest Build UUID: %{uuid} 8dbd243f-6bb7-4dc6-8a13-e24f6e197500 Target Images UUIDs: %{uuid} bbfbc8cc-77e3-4f2b-b1dd-5299552395e8fbeb8135-af01-43b4-ab1b-a298c060815b8aea88dd-f475-43c8-8bec-787db52a8f71 recreate: [root@hp-sl2x170zg6-01 ~]# aeolus-image build --target ec2,vsphere,rhevm --template audrey-client-RHEL6-rhevm-vsphere.tpl Image Build Target Image Target Status ------------------------------------ ------------------------------------ ------------------------------------ ------- -------- 402abe36-c4ed-4f74-9ae2-6668bbf4633a b26ebf39-7863-44c3-ac9c-7f9bc03fe5d1 3140b487-9f34-44b1-bd79-5e42e68fc346 ec2 BUILDING 402abe36-c4ed-4f74-9ae2-6668bbf4633a b26ebf39-7863-44c3-ac9c-7f9bc03fe5d1 77840b1f-2075-4a69-9388-ec0edf7c8693 vsphere BUILDING 402abe36-c4ed-4f74-9ae2-6668bbf4633a b26ebf39-7863-44c3-ac9c-7f9bc03fe5d1 f95729f7-bea0-40cf-8375-a485f1ebf184 rhevm BUILDING [root@hp-sl2x170zg6-01 ~]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.8.0-26.el6.noarch aeolus-conductor-0.8.0-26.el6.noarch aeolus-conductor-doc-0.8.0-26.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch aeolus-configure-2.5.0-13.el6.noarch aeolus-all-0.8.0-26.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch
Patch created: https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008854.html
Pushed to 0.9-maint: commit 4a4fcd5984206dfe0cfba8edc3627c6b1b8a62e7 BZ 790548 add spacing if there are multiple target image uuids
4a4fcd5 in aeolus-conductor-0.8.0-28
Created attachment 564930 [details] uuid_space
rpm -qa|grep aeolus aeolus-conductor-daemons-0.8.0-33.el6.noarch aeolus-configure-2.5.0-14.el6.noarch rubygem-aeolus-image-0.3.0-8.el6.noarch aeolus-conductor-0.8.0-33.el6.noarch rubygem-aeolus-cli-0.3.0-9.el6.noarch aeolus-conductor-doc-0.8.0-33.el6.noarch aeolus-all-0.8.0-33.el6.noarch
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