Bug 518292

Fixed in:
condor-7.3.2-0.5

How could I test this issue?

Collector is running:
$ ps aux | grep coll
condor   28491  0.4  0.1  51400  9136 ?        Ssl  11:44   0:04 condor_collector -f

This doesn't work:
$ condor_restart -collector localhost
Found no ClassAds when querying pool (local)
Can't find address for collector localhost.localdomain
Perhaps you need to query another pool.

also these don't work:
$ condor_restart -collector `hostname`
Found no ClassAds when querying pool (local)
Can't find address for collector HOSTNAME
Perhaps you need to query another pool.

$ condor_restart `hostname` -collector
Found no ClassAds when querying pool (local)
Can't find address for collector HOSTNAME
Perhaps you need to query another pool.

$ condor_restart localhost -collector
Found no ClassAds when querying pool (local)
Can't find address for collector localhost.localdomain
Perhaps you need to query another pool

$ condor_restart -name localhost -collector
Found no ClassAds when querying pool (local)
Can't find address for collector localhost.localdomain
Perhaps you need to query another pool.

$ condor_restart -name `hostname` -collector
Found no ClassAds when querying pool (local)
Can't find address for collector HOSTNAME
Perhaps you need to query another pool.

"condor_status -pool `hostname`" works as I expect, it writes list of slots only on HOSTNAME.
There is "condor_status -pool <name> Get information from collector <name>" in documentation, so with which parameter should I run condor_restart? Is it pool name, collector name or hostname?
I've tested it on Rhel 5.3 condor 7.4.0-0.3.el5.

--------------------------------
On Rhel 5.4 condor-7.2.2-0.9.el5 it looks different:

$ condor_restart -collector `hostname`
Unrecognized daemon type while resolving names
Use "-help" to see usage information

$ condor_restart `hostname` -collector
Unrecognized daemon type while resolving names
Use "-help" to see usage information

$ condor_restart -name `hostname` -collector
Unrecognized daemon type while resolving names
Use "-help" to see usage information

You can use any daemon, not just the collector (ie condor_restart -subsystem job_router) not just the collector.  The daemon must be registered with the collector (condor_status -any will show registered collectors).

Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
please see bug summary.

Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1,8 @@
-please see bug summary.+Grid bug fix
+
+C: 
+C: Attempting to specify a specific node when issuing a condor_restart fails.
+F:
+R:
+
+MORE INFORMATION REQUIRED FOR RELEASE NOTE

Tested on RHEL 5.4/4.8 x x86_64/i386 with condor-7.4.1-0.5 and it works. -->VERIFIED

Tested by command: condor_restart -subsystem <name>
where <name> is collector, master, schedd, startd or negotiator.

I tested it again for sure with command condor_restart -subsystem collector <remote machine> and it doesn't work. -->ASSIGNED

Performing a:

condor_restart -subsystem job_router <remote host>

Would produce an error:

Can't find address for collector <remote host>
Perhaps you need to query another pool.

Because the tools were not properly performing a lookup for the collector in a pool.  Modified the tools to properly lookup collectors in a pool, and now remote subsystems can be restarted/reconfigured as expected.

On advice from Jeff, this bug has been removed from the relnotes. Flag set to - (denied).

LKB

Tested on RHEL 5.4/4.8 x x86_64/i386 with condor-7.4.1-0.7 and it works for master, schedd, startd or negotiator.
-->VERIFIED and create new BZ for collector.

Tested by command: condor_restart -subsystem <name> -name <target hostname>
where <name> is collector, master, schedd, startd or negotiator.

The fix for this bug was included in the MRG 1.2 release.

The fix for this bug was included in the MRG 1.2 release.