Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 497854

Summary: Condor tools only consult local address or daemon classad files
Product: Red Hat Enterprise MRG Reporter: Matthew Farrellee <matt>
Component: condorAssignee: Matthew Farrellee <matt>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 1.1.1CC: lans.carstensen
Target Milestone: 1.2   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-10 15:06:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthew Farrellee 2009-04-27 15:12:25 UTC 
Two default configuration options have daemons dropping information about how they can be contacted into the local file system on a machine.

<SUBSYS>_ADDRESS_FILE
<SUBSYS>_DAEMON_AD_FILE

These files mostly represent an optimization - they let tools on a local machine avoid contacting the Collector to communicate with daemons on the local machine.

When a tool, such as condor_q, tries to locate the Schedd it consults SCHEDD_ADDRESS_FILE and SCHEDD_DAEMON_AD_FILE. In a HA Schedd setup those files may be stale. The result is condor_q fails to find the Schedd, which it could easily locate with a lookup in the Collector.

Two possibilities: 1) make the tools fall back to doing a Collector lookup, 2) disable the cache files

However, this is mostly an issue with the HA Schedd. So it would also be possible to just put the SCHEDD_ADDRESS_FILE and SCHEDD_DAEMON_AD_FILE into the SPOOL, which is shared in a HA setup.
Comment 1 Matthew Farrellee 2009-06-10 15:06:51 UTC 

*** This bug has been marked as a duplicate of bug 486487 ***