Bug 745523

Summary:	configd won't timeout if no wallaby to contact
Product:	Red Hat Enterprise MRG	Reporter:	Robert Rati <rrati>
Component:	condor-wallaby-client	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Tomas Rusnak <trusnak>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	ltoscano, matt, trusnak
Target Milestone:	2.1
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	condor-wallaby-client-4.1.1-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-27 19:12:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robert Rati 2011-10-12 15:19:54 UTC

Description of problem:
The configd won't timeout looking for the wallaby store agent.  When run as a daemon it's not such a horrible thing, but when run with -r (to retrieve a config), this is bad as the command will never time out if there isn't a contactable wallaby.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Robert Rati 2011-10-12 18:51:53 UTC

Added CONFIGD_WALLABY_CONNECT_TIMEOUT, which defaults to 60 seconds, to control
how long the configd will wait to contact wallaby on start up.  This most
evident when doing a one-off pull of the configuration.

Fixed on:
BZ745523-configd-timeout-no-wallaby

Comment 3 Luigi Toscano 2011-10-13 16:23:48 UTC

Just to be sure, does CONFIGD_WALLABY_CONNECT_TIMEOUT=0 mean "timeout immediately if not found" or "do not timeout"?

Comment 4 Robert Rati 2011-10-13 21:15:22 UTC

0 would result in "timeout immediately if not found", which would be immediately because it takes a few seconds to find the agent.  A timeout of 0 isn't a good idea, and even if did somehow succeed could produce a spurious error message in the logs.

Comment 5 Tomas Rusnak 2012-01-06 13:22:48 UTC

Reproduced on:

condor-wallaby-client-4.0-4.el5

# time condor_configd -r

real	4m34.851s
user	0m0.429s
sys	0m0.176s

Retested on all supported platforms x86_64, x86 on RHEL5,RHEL6:

condor-wallaby-client-4.1.2-1

# time condor_configd -r
Error: Unable to retrieve configuration

real	1m0.929s
user	0m0.944s
sys	0m0.338s

Retrieving configuration timeout happened after default 60sec in condor_configd.

>>> VERIFIED