Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 905460

Summary: aeolus-configure provider failure is not logged
Product: [Retired] CloudForms Cloud Engine Reporter: Aaron Weitekamp <aweiteka>
Component: aeolus-configureAssignee: Mike Orazi <morazi>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1.0   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
aeolus-configure.log none

Description Aaron Weitekamp 2013-01-29 13:39:58 UTC
Created attachment 689831 [details]
aeolus-configure.log

Description of problem:
If provider setup fails during aeolus-configure exits with status 1 but does not log what failed.
Log: /var/log/aeolus-configure/aeolus-configure.log

Version-Release number of selected component (if applicable):
CFCE 1.1
[root@qeblade40 ~]# rpm -qa |grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-configure-2.8.11-1.el6cf.noarch
aeolus-conductor-doc-0.13.26-1.el6cf.noarch
aeolus-conductor-0.13.26-1.el6cf.noarch
aeolus-all-0.13.26-1.el6cf.noarch
aeolus-conductor-daemons-0.13.26-1.el6cf.noarch
rubygem-aeolus-cli-0.7.7-1.el6cf.noarch


How reproducible:
always

Steps to Reproduce:
1. point to invalid storage in /etc/aeolus-configure/nodes/<provider>_configure
2. run aeolus-configure
  
Actual results:
Returns exit status 1 but no failure indicated in logs. In this case both RHEV 3.0 and 3.1 were defined, only RHEV 3.0 storage was offline and yet both RHEV providers failed. There is no mention of RHEV in /var/log/aeolus-configure/aeolus-configure.log.

Expected results:
Attempt and failure to configure provider should be logged.