Description of problem:
The only supported method of creating a new vsphere or rhevm cloud provider in v1.1 is to use aeolus-configure -p. See https://bugzilla.redhat.com/show_bug.cgi?id=867928

However, re-running aeolus-configure -p vsphere|rhevm reverts authorization mode to database. So if in LDAP mode, one needs to again edit the auth mode files and restart services after running aeolus-configure.
1. edit /etc/aeolus-conductor/settings.yml  
2. edit /etc/ldap_fluff.yml     
3. `aeolus-services restart`

Re-running aeolus-configure should only affect the provider creation.


Version-Release number of selected component (if applicable):
1.1
aeolus-configure-2.8.9-1.el6cf.noarch

How reproducible:
100%

Steps to Reproduce:
*assumes configured aeolus install in LDAP mode.*
1. edit /etc/aeolus-configure/nodes/rhevm_configure or /etc/aeolus-configure/nodes/vsphere_configure
2. run aeolus-configure -p vsphere|rhevm  

Actual results:
Files /etc/aeolus-conductor/settings.yml and /etc/ldap_fluff.yml have reverted to default. LDAP users cannot authenticate. Auth mode must be reset.
1. edit /etc/aeolus-conductor/settings.yml  
2. edit /etc/ldap_fluff.yml     
3. `aeolus-services restart`