Description of problem: When EC2Enchanced is added to a node, activation of the configuration returns an error: ----------------------------------- # condor_configure_pool --activate The configuration is not valid Node: rhel5ec2.vmmrg Unsatisfied parameter dependencies: LIBEXEC Configuration not activated ----------------------------------- Version-Release number of selected component (if applicable): ruby-wallaby-0.6.1-2.el5 wallaby-utils-0.6.1-2.el5 python-wallabyclient-3.0-1.el5 condor-wallaby-base-db-1.2-1.el5 condor-wallaby-client-3.0-1.el5 condor-wallaby-tools-3.0-1.el5 wallaby-0.6.1-2.el5 Expected results: LIBEXEC should have a default value.
Removed LIBEXEC and the param deps from the db. LIBEXEC is different on windows, so it can't be included in the db. Fixed in: condor-wallaby-base-db-1.2-2
LIBEXEC is no more a parameter, condor relies on the system-defined variable. After the addition of the EC2Enhanced feature is correctly executed. Verified on RHEL 5.5, i386/x86_64, MRG 1.3: condor-wallaby-base-db-1.4-5 condor-wallaby-client-3.6-6 condor-wallaby-tools-3.6-6 python-wallabyclient-3.6-6 ruby-wallaby-0.9.18-2 wallaby-0.9.18-2 wallaby-utils-0.9.18-2