Description of problem: [root@qeblade32 ~]# aeolus-image import --help Usage: aeolus-image import [command options] Options: -d, --id ID id for a given object -r, --description NAME description (e.g. "<image><name>MyImage</name></image>" or "/home/user/myImage.xml") -A, --account NAME,NAME name of specific account to import to -h, --help Get usage information for this command Examples: aeolus-image import --account my-ec2 --id $ami_id # import an AMI from the specified provider aeolus-image import --account my-ec2 --id $ami_id --description '<image><name>My Image</name></image>' # import an AMI from the specified provider aeolus-image import --account my-ec2 --id $ami_id --description <path_to_xml_file> # import an AMI from the specified provider RHEV: Enter the template id for the provider image id. The template id can be found through the RHEV REST API. For example: curl https://rhevm.example.org:8443/api/templates --user user@rhevm_domain:password N.B. Aeolus Credentials should be defined in the configuration file ~/.aeolus-cli [root@qeblade32 ~]# aeolus-image import --account ec2-us-east-1_AKIAJ557U7P7OIHRV2EQ --id ami-4fd00526 --description "wesAmiCLI" ERROR: The given image description does not conform to the xml schema, see below for specific details: - Internal error: no state ERROR: Argument Error => Invalid description [root@qeblade32 ~]# aeolus-image import --account ec2-us-east-1_AKIAJ557U7P7OIHRV2EQ --id ami-4fd00526 ERROR: InsufficientParametersSupplied => Please specify an environment [root@qeblade32 ~]# aeolus-image import --account ec2-us-east-1_AKIAJ557U7P7OIHRV2EQ --id ami-4fd00526 -E default Warning, invalid option: -E See `aeolus-image import -h` for usage information.
Pushed to master as 15ef29d3528ee1814d7841b525e7dab50e1de9de
in build.. moving to on_qa
Beta2 contains rubygem-aeolus-cli-0.3.0-10.el6, while the fix is in rubygem-aeolus-cli-0.3.0-11.el6. Until the fixed package lands in a Beta2 puddle (not a nightly repo) MODIFIED is still appropriate.
Moving back to MODIFIED pending a fix is included in a beta2 puddle
Moving back to on_qa as there is no upcoming puddle
[root@qe-blade-08 ~]# aeolus-image import --account ssachdev --id ami-4fd00526 -E default Image Build Target Image Provider Image Status ------------------------------------ ------------------------------------ ------------------------------------ ------------------------------------ -------- 7720b929-6496-43b0-8917-61e3addf69c2 7b1ec7a3-95ad-4ef4-9abd-0f3e281e5da7 68f12783-7d5c-4b06-8c7f-288166313a29 64f34732-f54a-435a-b7de-25b651d116bb COMPLETE ========================================================= rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-39.el6.noarch rubygem-aeolus-cli-0.3.0-12.el6.noarch aeolus-all-0.8.0-39.el6.noarch aeolus-conductor-0.8.0-39.el6.noarch rubygem-aeolus-image-0.3.0-11.el6.noarch aeolus-configure-2.5.0-16.el6.noarch aeolus-conductor-daemons-0.8.0-39.el6.noarch
aeolus-image import --account ssachdev --id ami-31d41658 -E default --description "<image><name>xml-name</name></image>" Image Build Target Image Provider Image Status ------------------------------------ ------------------------------------ ------------------------------------ ------------------------------------ -------- 18ba2a44-f1d8-420a-a002-701652ae51ae a4873e8c-749d-4bf4-b4a5-e98714d7d513 b57548ef-2144-45e5-a80f-264de0507bf5 f9481267-cf73-4f8d-81d8-234a407e9fae COMPLETE =========================================================================== aeolus-image import --account ssachdev --id ami-31d41658 -E default --description /root/temp.tpl Image Build Target Image Provider Image Status ------------------------------------ ------------------------------------ ------------------------------------ ------------------------------------ -------- 9adb6b3e-66ae-4eeb-b915-fab5d7864c00 818523f5-80a6-4fba-8758-b3271e7068f4 cbacf2fb-93f1-46e9-94b8-776be08923cb 789bf13b-42d5-4f50-a76d-32501c7b501f COMPLETE
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