Bug 751113

Summary: unable to configure rhevm
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-configureAssignee: Richard Su <rwsu>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, dajohnso, deltacloud-maint, dgao, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 20:43:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description wes hayutin 2011-11-03 14:57:49 UTC
Description of problem:

[root@qeblade31 nodes]# aeolus-configure -d -v -p rhevm
Launching aeolus configuration recipe...
info: Loading facts in oauth
Failed to parse template aeolus/rhevm.json: Could not find value for 'rhevm_push_timeout' at /usr/share/aeolus-configure/modules/aeolus/manifests/profiles/rhevm.pp:17 on node qeblade31.rhq.lab.eng.bos.redhat.com
[root@qeblade31 nodes]# 



[root@qeblade31 nodes]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.6.0-0.20111029030732git7410602.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111028152758git7063136.fc15.noarch
aeolus-conductor-0.6.0-0.20111029030732git7410602.fc15.noarch
aeolus-conductor-daemons-0.6.0-0.20111029030732git7410602.fc15.noarch
aeolus-all-0.6.0-0.20111029030732git7410602.fc15.noarch
rubygem-aeolus-image-0.1.0-4.20111024205454git6b2b696.fc15.noarch
aeolus-configure-2.3.0-0.20111028220920gitf01b051.fc15.noarch
[root@qeblade31 nodes]#

Comment 1 Richard Su 2011-11-03 16:38:22 UTC
Do you have this line in /etc/aeolus-configure/nodes/rhevm?

  rhevm_push_timeout: 1800

It is new in 0.5.0.

Comment 4 errata-xmlrpc 2012-05-15 20:43:33 UTC
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-0586.html