Hide Forgot
Description of problem: I think it will be fine to have possibility to add new parameter and feature from condor_configure_pool if it doesn't exist. I think it's not comfortable now to get error message from condor_configure_pool, then run condor_configure_store and then run condor_configure_pool again to set parameter value/feature. Version-Release number of selected component (if applicable): condor-wallaby-tools-4.0-4.el5 Now: $ condor_configure_pool -n `hostname` -a -p JOB_SERVER.JOB_SERVER_DEBUG Value for "JOB_SERVER.JOB_SERVER_DEBUG": D_FULLDEBUG Apply these changes [Y/n] ? Error: Problem adding parameters (134218753, Invalid parameters for the identity group for hostname: ["JOB_SERVER.JOB_SERVER_DEBUG"]) $ condor_configure_store -a -p JOB_SERVER.JOB_SERVER_DEBUG -> open $EDITOR $ condor_configure_pool -n `hostname` -a -p JOB_SERVER.JOB_SERVER_DEBUG -> set value Then: $ condor_configure_pool -n `hostname` -a -p JOB_SERVER.JOB_SERVER_DEBUG Value for "JOB_SERVER.JOB_SERVER_DEBUG": D_FULLDEBUG Apply these changes [Y/n] ? Error: Problem adding parameters (134218753, Invalid parameters for the identity -> open $EDITOR -> add JOB_SERVER.JOB_SERVER_DEBUG to store -> set value
The ccp pool is not supposed to add new elements to the store. It is for applying configurations only, and two separate tools allows separation of responsibilities (a role for managing what is available to configure in the store (ccs), and a role for configuring the pool(ccp)). Having ccp add entities to the store complicates the tools and muddies the waters between the two tools.
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.