Description of problem: In some cases condor_configure_store/pool give wrong return code E.g. 1.) ccs/p should return other than zero return code # condor_configure_store -a -f Feature; echo $? Adding feature "Feature" Error: Failed to add feature "Feature" (67109121, Feature name Feature is already taken) 0 # condor_configure_store -e -f Feature; echo $? Error: Failed to find feature "Feature" (67109889, Feature named Feature not found) 0 # condor_configure_store -a -f Feature; echo $? Adding feature "Feature" The store does not know about the following items: Parameter PP Should the above be added to the store [Y/n]? n The following errors were reported updating "Feature": 134218753: Invalid parameters supplied to feature Feature: PP 0 # condor_configure_pool -l -n node; echo $? Error: Failed to find node "node" 0 2.) ccs/p should return zero return code # condor_configure_store -d -f Feature; echo $? Warning: About to delete the following entities from the store: Features: Feature Proceed to delete the above entities from the store [y/N]? <Enter> 1 Version-Release number of selected component (if applicable): condor-wallaby-tools-4.0-4 wallaby-0.10.5-3
The listed cases have been handle appropriately and future cases should be handled as well. Fixed on master.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: Providing invalid arguments, or other invalid scenarios, to the condor_configure_pool/store tools C: The tools would indicate error, but the return value would indicate success F: The tools properly exit with an non-zero value in error cases R: The tools will return non-zero return codes when the actions did not succeed.
Tested with: condor-wallaby-tools-4.0-6 Tested on: RHEL5 i386,x86_64 - passed RHEL6 i386,x86_64 - passed >>> VERIFIED
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0889.html