Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. I have provider accounts added for all providers ec2 , rhevm and vsphere 2. 3. Actual results: aeolus-image list --accounts Name Provider Provider Type ---- -------- ------------- Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.13.16-1.el6cf.noarch aeolus-conductor-daemons-0.13.16-1.el6cf.noarch rubygem-aeolus-cli-0.7.3-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.16-1.el6cf.noarch aeolus-conductor-0.13.16-1.el6cf.noarch aeolus-configure-2.8.8-1.el6cf.noarch
This was caused due to API changes in conductor. Rather than update the CLI to adhere to these new changes I have changed the default behaviour to act in the same way as v1.0 API.
I "fixed" the providerimages command in the CLI to account for the API change already, so we'll also need to revert that commit. I completely agree with this approach. Maintaining the API compatibility is the right solution. See: https://github.com/aeolusproject/aeolus-cli/pull/1
On conductor 1.1 as 708ac20, b859a3c
On aeolus-cli 1.1 as 699be4a
# aeolus-image list --accounts Name Provider Provider Type ----------- ------------- ------------- mock mock mock aziza_rhevm rhevm-default rhevm verified: rpm -qa | grep aeolus aeolus-conductor-doc-0.13.20-1.el6cf.noarch rubygem-aeolus-cli-0.7.5-1.el6cf.noarch aeolus-all-0.13.20-1.el6cf.noarch aeolus-conductor-0.13.20-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.8.9-1.el6cf.noarch aeolus-conductor-daemons-0.13.20-1.el6cf.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-1516.html