Bug 575147 – condor_master can't start additional schedd's without a restart

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 575147 - condor_master can't start additional schedd's without a restart

Summary:	condor_master can't start additional schedd's without a restart

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	condor (Show other bugs)
Sub Component:
Version:	1.2
Hardware:	All Linux

Priority	urgent Severity medium
Target Milestone:	1.3
Target Release:	---
Assigned To:	Robert Rati
QA Contact:	Luigi Toscano
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-03-19 11:33 EDT by Scott Spurrier
Modified:	2018-10-27 10:50 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	7.4.3-0.8
Doc Type:	Bug Fix
Doc Text:	Previously, "condor_reconfig" didn't launch the newly configured condor schedduler daemon and a restart of the condor_master process was required. With this update, "condor_reconfig -master" allows the user to launch any additional daemons added to the configuration.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-10-14 12:01:43 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2010:0773	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3	2010-10-14 11:56:44 EDT

Groups: None (edit)

Description Scott Spurrier 2010-03-19 11:33:58 EDT

Description of problem:

1.  You want to start up an additional condor_schedd in a multiple condor_schedd and HA environment.
2.  You add configuration for the condor_schedd to both HA nodes.
3.  "condor_reconfig" doesn't launch the newly configured condor_schedd.  A restart of the condor_master process is required.

This requires you to perform an unnecessary HA failover, which is an expensive and production-impacting process.  Unless I'm missing a way to accomplish this by other means.

How reproducible:

100%

Steps to Reproduce:

See above.

Actual results:

See above

Expected results:

"condor_reconfig -master" should launch any additional daemons added to the configuration.

Comment 1 Robert Rati 2010-04-09 11:18:24 EDT

A condor_reconfig -master will now stop and daemons removed from, and start daemons added from, DAEMON_LIST since master was last configured/started.

Fixed in:
condor-7.4.3-0.8

Comment 4 Luigi Toscano 2010-10-06 12:03:51 EDT

condor_master acts as decribed in comment 1.

Verified on RHEL 4.8/5.5, i386,x86_64.
condor-7.4.4-0.16

Comment 5 Florian Nadge 2010-10-07 09:38:43 EDT

    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, "condor_reconfig" didn't launch the newly configured condor schedduler daemon and a restart of the condor_master process was required. With this update, "condor_reconfig -master" allows the user to launch any additional daemons added to the configuration.

Comment 7 errata-xmlrpc 2010-10-14 12:01:43 EDT

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

Note You need to log in before you can comment on or make changes to this bug.