condor-remote-configuration-server-1.0-14.el5 Adding ha_central_manager to a node adds ha_central_manager, central_manager, negotiator, collector. Deleting ha_central_manager only deletes ha_central_manager. # condor_configure_node -l -n node Configuration for node: ha_central_manager central_manager negotiator collector scheduler_name = ha-schedd@ default_schedd_isha = True additional_scheds = sched-00,sched-01 collector_name = Pool qmf_broker = broker startd # condor_configure_node -d -n node -f ha_central_manager Modify the pool description for this node [y/N] ? Change the broker information this node uses to communicate with the Management Console [y/N] ? Save this configuration [y/N] ? y Configuration saved Refreshing node configurations # condor_configure_node -l -n node Configuration for node: central_manager negotiator collector default_schedd_isha = True collector_name = Pool qmf_broker = broker startd # condor_configure_node -d -n node -f central_manager Modify the pool description for this node [y/N] ? Change the broker information this node uses to communicate with the Management Console [y/N] ? Save this configuration [y/N] ? y Configuration saved Refreshing node configurations # condor_configure_node -l -n node Configuration for node: negotiator collector default_schedd_isha = True collector_name = Pool qmf_broker = broker startd
The tools will look for parameters that must be set by a feature when removing a feature. It will not handle the case were a parameter, that is part of a feature but is not required to be set for the parameter to be used, is added to a node/group. Fixed in: condor-qmf-config-tools-2.1-0.1
Tested with shared parameters ALLOW_ADMINISTRATOR: HACentralManager, Master CONDOR_HOST: HACentralManager, Master COLLECTOR_NAME: Collector, Master ALLOW_NEGOTIATOR: HACentralManager, Negotiator ALLOW_NEGOTIATOR_SCHEDD: BaseScheduler, HACentralManager COLLECTOR_HOST: Collector, HACentralManager JOB_HOOKS_PORT: JobHooks, LowLatency SPOOL: JobQueueLocation, Scheduler STARTD_JOB_EXPRS: ExecuteNode, ExecuteNodeDedicatedPreemption KILL: DedicatedResource, ExecuteNode PREEMPT: DedicatedResource, ExecuteNode START: DedicatedResource, ExecuteNode SUSPEND: DedicatedResource, ExecuteNode STARTD_ATTRS: DedicatedResource, ExecuteNode WANT_SUSPEND: DedicatedResource, ExecuteNode WANT_VACATE: DedicatedResource, ExecuteNode CONTINUE: DedicatedResource, ExecuteNode on RHEL 5.5 x86_64/i386 with python-condorutils-1.4-5.el5 condor-wallaby-tools-3.6-5.el5 condor-wallaby-base-db-1.4-5.el5 condor-debuginfo-7.4.4-0.16.el5 condor-7.4.4-0.16.el5 condor-wallaby-client-3.6-5.el5 wallaby-0.9.18-2.el5 and it works. -->VERIFIED
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: Adding 'ha_central_manager' to a node adds 'ha_central_manager', 'central_manager', 'negotiator', and 'collector'. However, deleting 'ha_central_manager' only deleted the 'ha_central_manager'. With this update, deleting 'ha_central_manager' from a node successfully removes 'ha_central_manager', 'central_manager', 'negotiator', and 'collector'.
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/RHSA-2010-0773.html