Bug 850420 - [RFE] aeolus-configure: Require proper error message for multiple invalid parameters in config file.
[RFE] aeolus-configure: Require proper error message for multiple invalid par...
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-configure (Show other bugs)
1.1.0
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Mike Orazi
Rehana
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-21 10:35 EDT by Aziza Karol
Modified: 2012-09-28 13:12 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
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: ---


Attachments (Terms of Use)

  None (edit)
Description Aziza Karol 2012-08-21 10:35:19 EDT
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
I updated the vsphere configuration file with invalid parameters as below.
 #cat  /etc/aeolus-configure/nodes/vsphere_configure
default:
        # Uncomment and provide values to match your vSphere environment.
        # Values below are examples.
          detacloud_provider: vsphere.server.com
          urname: username
          password: password
          datastore: datastore
          network_name: network_name

and run aeolus-configure  -p  vsphere.
  
Actual results:
only the username is considerd as the invalid parameter.

# aeolus-configure  -p  vsphere
Launching aeolus configuration recipe...
Invalid parameter urname on node dell-pe1950-1.rhts.eng.rdu.redhat.com



Expected results:
A proper message with all the invalid paramaters must be displayed.
so a proper error message for handling multiple invalid paramaters in config file is required.

Additional info:
rpm -qa | grep aeolus
rubygem-aeolus-image-0.6.0-0.20120820230032git25b7466.fc16.noarch
aeolus-configure-2.8.0-0.20120820230025gitbdcd549.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120821030009git92d81d1.fc16.noarch
rubygem-aeolus-cli-0.7.0-0.20120820230026gitd64d64f.fc16.noarch
aeolus-conductor-0.13.0-0.20120821030009git92d81d1.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120821030009git92d81d1.fc16.noarch
aeolus-all-0.13.0-0.20120821030009git92d81d1.fc16.noarch

Note You need to log in before you can comment on or make changes to this bug.