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

Bug 851222

Summary:	configd should detect if there are more wallaby agents on broker
Product:	Red Hat Enterprise MRG	Reporter:	Lubos Trilety <ltrilety>
Component:	condor-wallaby-client	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Lubos Trilety <ltrilety>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.2	CC:	matt, rrati
Target Milestone:	2.3
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	condor-wallaby-5.0.3-1	Doc Type:	Bug Fix
Doc Text:	Cause: Multiple wallaby-agents running against the broker the configd is talking to Consequence: The configd would choose the first one, which may not be the one desired Fix: The configd will exit with a notification in its log file if it finds more than 1 wallaby-agent running Result: The configd will only run if there is 1 wallaby-agent running on the broker	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-06 18:45:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lubos Trilety 2012-08-23 14:16:01 UTC

Description of problem:
Configd should detect if there are two or more wallaby agents connected to the broker. In such case it should log clear error, something like:
"I'm refusing to run against two or more agents; kill one of these"

As it is now configd chooses the first connected wallaby agent without logging any error.

Version-Release number of selected component (if applicable):
condor-wallaby-client-4.1.3-1

How reproducible:
100%

Steps to Reproduce:
1. set two wallaby agents so they connect to the same broker
2. start condor_configd see logs
  
Actual results:
no error message configd chooses the first connected wallaby agent

Expected results:
error message about more wallaby agents connected to the broker

Additional info:

Comment 1 Robert Rati 2012-09-24 21:36:50 UTC

The configd will log a message to it's log and exit with a status of 1 if it detects more than 1 store on the broker.

Fixed upstream on:
BZ851222-multiple-stores

Comment 4 Lubos Trilety 2012-12-17 16:41:42 UTC

Tested with:
condor-wallaby-client-5.0.4-1

Tested on:
RHEL6 i386,x86_64
RHEL5 i386,x86_64

$ tailf Configd
...
ERROR: Multiple configuration stores detected.  Refusing to run against 2 or more configuration stores.

>>> verified

Comment 6 errata-xmlrpc 2013-03-06 18:45:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0564.html