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

Bug 543021

Summary:	Unable to restart collector with condor_restart on remote node
Product:	Red Hat Enterprise MRG	Reporter:	Martin Kudlej <mkudlej>
Component:	condor	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Martin Kudlej <mkudlej>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.1	CC:	fnadge, matt
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, a collector could not be remotely restarted. With this update, the restart is possible and works as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-14 16:15:11 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 Martin Kudlej 2009-12-01 14:15:05 UTC

Description of problem:
Unable to restart collector remotely by condor_restart -subsystem collector -name <target hostname>

see https://bugzilla.redhat.com/show_bug.cgi?id=518292#c11

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

How reproducible:
100%

Steps to Reproduce:
1. set up condor pool
2. condor_restart -subsystem collector -name <target hostname>

Comment 1 Robert Rati 2009-12-14 16:05:37 UTC

The issue was that the collector was using COLLECTOR_NAME as the name in it's daemon ad, which is assumed to be a resolvable hostname.  So if COLLECTOR_NAME was explicitly set to "Bob's Pool", the daemon ad's name would be "Bob's Pool", which obviously isn't resolvable.  The collector will now append @FQDN to the COLLECTOR_NAME if the COLLECTOR_NAME does not contain an @, otherwise it is assume the name is valid and will use whatever COLLECTOR_NAME is set to.  If COLLECTOR_NAME does not contain a resolvable hostname, then it will not be possible to restart/reconfig a collector remotely.

Fixed in build after:
condor-7.4.1-0.7.1

Comment 2 Matthew Farrellee 2010-01-04 18:25:51 UTC

Fixed in 7.4.2-0.1

Comment 3 Martin Kudlej 2010-05-11 14:06:30 UTC

I've tried it with condor-7.4.3-0.13.el5 and condor-7.4.3-0.11.el4 and it works. I cannot move this bug to modified, because those ones are still only devel packages.

Comment 4 Martin Kudlej 2010-06-11 12:23:48 UTC

Teste on RHEL5.5/4.8 x i385/x86_64 with condor-7.4.3-0.17 and it works. -->VERIFIED

Comment 5 Martin Prpič 2010-10-07 16:03:46 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, a collector could not be remotely restarted using the "condor_restart -subsystem collector -name <target hostname>" command. With this update, the restart is possible and works as expected.

Comment 6 Florian Nadge 2010-10-08 10:08:17 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously, a collector could not be remotely restarted using the "condor_restart -subsystem collector -name <target hostname>" command. With this update, the restart is possible and works as expected.+Previously, a collector could not be remotely restarted. With this update, the restart is possible and works as expected.

Comment 8 errata-xmlrpc 2010-10-14 16:15:11 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html