Users may experience an failure while attempting to configure a vSphere provider using the aeolus-configure command-line tool. While the cause is not yet known, vSphere may return an unexpected response code during provider configuration. Users experiencing this problem are recommended to re-configure the failing provider. For example, to re-configure vSphere one may issue the following command:
# aeolus-configure -p vsphere
Engineering will continue to investigate the problem and provide an update, if needed, at a later date.
Created attachment 644137[details]
aeolus debug archive
Description of problem:
/conductor/providers.xml occasionally returns 422 on vsphere provider creation, attached is the output from 'aeolus-debug'
Version-Release number of selected component (if applicable):
aeolus-configure-2.8.11-1.el6cf.noarch
How reproducible:
seems to be intermittent :(
Steps to Reproduce:
1. install 'aeolus-all'
2. run 'aeolus-configure -p ec2,mock,rhevm,vsphere' (the provider config files are in the attached archive)
Actual results:
configure fails as one of the dependencies fails; logging in conductor is possible, but the vsphere provider is not available and the temporary admin user is still in accounts list
Created attachment 647890[details]
aeolus-debug-20121119121749.tar.gz
Reproduced on CloudForms-1.1 RC1. Re-running 'aeolus-configure -p vsphere' and the problem goes away.
* aeolus-conductor-0.13.24-1.el6cf.src.rpm
* aeolus-configure-2.8.11-1.el6cf.src.rpm
Created attachment 644137 [details] aeolus debug archive Description of problem: /conductor/providers.xml occasionally returns 422 on vsphere provider creation, attached is the output from 'aeolus-debug' Version-Release number of selected component (if applicable): aeolus-configure-2.8.11-1.el6cf.noarch How reproducible: seems to be intermittent :( Steps to Reproduce: 1. install 'aeolus-all' 2. run 'aeolus-configure -p ec2,mock,rhevm,vsphere' (the provider config files are in the attached archive) Actual results: configure fails as one of the dependencies fails; logging in conductor is possible, but the vsphere provider is not available and the temporary admin user is still in accounts list