+++ This bug was initially created as a clone of Bug #719052 +++ Description of problem: The condor_configure_pool tool hides the name of the default group and displays "Internal Default Group" for each instance it would appear to the user. However, the condor_configure_pool tool only allows --default-group as a target for acting upon the default group. Should allow -g "Internal Default Group" as well. The tools are rewritten and they've lost this functionality. Maybe it is connected with bug 823589 but i don't think so. Version-Release number of selected component (if applicable): wallaby-utils-0.14.1-1.el5 condor-wallaby-base-db-1.21-1.el5 python-wallabyclient-5.0.1-3.el5 ruby-condor-wallaby-tools-5.0.1-3.el5 condor-wallaby-tools-5.0.1-3.el5 wallaby-0.14.1-1.el5 condor-wallaby-client-5.0.1-3.el5 ruby-wallaby-0.14.1-1.el5 python-wallaby-0.14.1-1.el5 condor_configure_pool -l -v -g "Internal Default Group" Console Connection Established... warning: group Internal Default Group does not exist
condor_configure_pool now accepts "internal default group" as a target. Fixed upstream on: BZ823591-internal-default-group-target
Retested with: python-wallaby-0.16.1-2.el6.noarch condor-wallaby-base-db-1.24-2.el6.noarch condor-wallaby-client-5.0.3-2.el6.noarch ruby-wallaby-0.16.1-2.el6.noarch condor-wallaby-tools-5.0.3-2.el6.noarch wallaby-utils-0.16.1-2.el6.noarch python-wallabyclient-5.0.3-2.el6.noarch wallaby-0.16.1-2.el6.noarch ruby-condor-wallaby-5.0.3-2.el6.noarch condor_configure_pool -l -v -g "Internal Default Group" Console Connection Established... Showing the following group: +++DEFAULT +++DEFAULT name: "+++DEFAULT" membership: [] features: ["NodeAccess", "Master"] params: {"CONDOR_HOST"=>"node1", "ALLOW_READ"=>"*", "QMF_BROKER_HOST"=>"node1", "ALLOW_WRITE"=>"*", "START"=>"true"} annotation: "The default group" The ccp is accepting "Internal Default Group" as a group parameter value. >>> VERIFIED