I ran into the following when configuring aeolus for a RHEV provider.

1, contents of /etc/aeolus-configure/nodes/rhevm_configure 

http://fpaste.org/BrLg/

2. Here is the result of aeolus-configure -p rhevm,ec2

http://fpaste.org/kgnw/

The errors and warnings thrown are:

err: 
/Stage[main]/Aeolus::Deltacloud::Core/Exec[deltacloud-core-startup-wait]/returns:
 change from notrun to 0 failed: nc -z localhost 3002 returned 1 instead of one 
of [0] at 
/usr/share/aeolus-configure/modules/aeolus/manifests/deltacloud/core.pp:27

warning: 
/Stage[main]/Aeolus::Profiles::Rhevm/Aeolus::Profiles::Rhevm::Instance[default]/Aeolus::Conductor::Provider[rhevm-default]/Web_request[provider-rhevm-default]:
 Skipping because of failed dependencies
warning: 
/Stage[main]/Aeolus::Profiles::Common/Aeolus::Conductor::Logout[temporary-administrative-user-288431777d9a69cd8794e05ffc165eba865f0e8f82ed7c44]/Web_request[temporary-administrative-user-288431777d9a69cd8794e05ffc165eba865f0e8f82ed7c44-conductor-logout]:
 Skipping because of failed dependencies
warning: 
/Stage[main]/Aeolus::Profiles::Common/Aeolus::Conductor::Destroy_temp_admins[after]/Exec[destroy_temp_admin-after]:
 Skipping because of failed dependencies

3. If I rerun `aeolus-configure -p rhevm` afterwards it sets up the RHEV 
provider without errors.

http://fpaste.org/iQUF/

Did I do something wrong? Why would the second time succeed with no changes in 
the environment?

-James

Reply via email to