Description of problem: It's been said that (a) testing the Provider tests the Provider account is valid. It's been said you can (b) test the Provider Account directly. However for (a) you can test for successfully for different provider regions successfully even though the Provider Account might be set up ofr only one of those regions. So that's confusing. For the (b) claim there is no Test button on the "Provider Account" tab. There should be one there. If the test is currently in Provider then it needs to be moved to Provider Account. Provider test should test for connection to the provider and a separate Provider Account test should confirm credentials. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Angus you had some comments for this bug
making sure all the bugs are at the right version for future queries
fixed in commit ad614b734c05b688bf9602243596417e74d6836d
Provider test and Provider Account test option is available for each provider. Provider test tests for connection to the provider. Provider Account test confirm credentials. verified on: [root@nec-em6 templates]# rpm -qa | grep aeolus aeolus-conductor-doc-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch aeolus-all-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch aeolus-conductor-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch aeolus-conductor-daemons-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.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