Hide Forgot
Description of problem: Example.. [root@cf-cloudforms9 log]# aeolus-cli import --provider sprec2 --target ec2 --description '<image><name>ami-5ef90237</name></image>' --id ami-5ef90237 description is also failing in the webui... https://bugzilla.redhat.com/show_bug.cgi?id=761282
I have tested it with mock and rhevm provider and it works. pblaho@f16:~/Workspace/aeolus-cli(bz-766139)$ sudo rpm -qa | grep aeolus [sudo] password for pblaho: 121:aeolus-configure-2.4.0-3.fc16.noarch 156:aeolus-conductor-doc-0.7.0-4.fc16.noarch 506:rubygem-aeolus-image-0.2.0-1.fc16.noarch 511:aeolus-all-0.7.0-4.fc16.noarch 847:aeolus-conductor-daemons-0.7.0-4.fc16.noarch 1344:rubygem-aeolus-cli-0.2.0-3.fc16.noarch 1382:aeolus-conductor-0.7.0-4.fc16.noarch
can you post ur command and doc on description if you have it
OK, I have tested it now (I already have an ec2 access) with aeolus-cli import --provider_account ec2-east --id ami-fef01297 aeolus-cli import --provider_account ec2-east --id ami-fef01297 --description "<image><name>xml-name</name></image>" aeolus-cli import --provider_account ec2-east --id ami-fef01297 --description ~/workspace/templates/import.tpl aeolus-cli import --provider_account ec2-east --id ami-fef01297 --description ~/workspace/templates/fedora15.tpl it works for first 3 commands as expected The last command do not create correct description because provided xml file do not mimic <image><name>NAME</name></image> structure. Works the same for other tested providers (mock and rhevm) mzatko is working on https://bugzilla.redhat.com/show_bug.cgi?id=747719 which will contain code for validating input parameters included xml structure from --description parameter. When it will be done this will be resoved. ----- sudo rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-0.20111220094209gitdd1bab7.fc16.noarch aeolus-conductor-doc-0.8.0-0.20111220154105git4f380bf.fc16.noarch rubygem-aeolus-cli-0.3.0-0.20111220094150git769a835.fc16.noarch aeolus-conductor-daemons-0.8.0-0.20111220154105git4f380bf.fc16.noarch aeolus-all-0.8.0-0.20111220154105git4f380bf.fc16.noarch aeolus-conductor-0.8.0-0.20111220154105git4f380bf.fc16.noarch aeolus-configure-2.5.0-0.20111220094137git3d8c09b.fc16.noarch
OK, tested against master branch with new patch for https://bugzilla.redhat.com/show_bug.cgi?id=747719 Works as expected.
[root@hp-bl260cg5-01 ~]# aeolus-image import --provider_account ssachdev --id ami-31d41658 Image: 547fc6ed-a455-42e2-9013-6acbe8377ff8 Build: 247071d8-050f-4ccd-bd99-880d452e1335 Target Image: 7d7a94c6-7c43-426c-a2fc-a2823201537b Provider Image: 839c8ea3-1f66-4153-be5b-31a756732c59 Status: COMPLETE ================================================================= [root@hp-bl260cg5-01 ~]# aeolus-image import --provider_account ssachdev --id ami-31d41658 --description "<image><name>xml-name</name></image>" Image: 6cdb2674-55ab-4246-a34f-32a60f0a0a9c Build: 7c7ca1e0-3d12-48b8-b932-b6e729310632 Target Image: 53e59d91-5cea-4538-bcaa-438163a57ef3 Provider Image: c4dbaa68-d50b-4d1d-a1ad-976ce45d8025 Status: COMPLETE ======================================================================== [root@hp-bl260cg5-01 ~]# aeolus-image import --provider_account ssachdev --id ami-31d41658 --description /root/temp.tpl Image: fb391a90-c62e-4ddb-8c02-a79e66be4bed Build: 71722436-d2d5-4309-8523-693d1432e819 Target Image: cc3d5f21-0e51-4f7d-91ad-070ff87d6ac4 Provider Image: f8464433-ddec-476e-a524-fbac26568bdb Status: COMPLETE ==================================================== Import works. rpm -qa|grep aeolus aeolus-conductor-doc-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-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
These bugs are verified, removing from ce-sprint
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-0591.html