Re: [HTCondor-users] Procedure for upgrading between feature releases

["Weatherby,Gerard" <gweatherby@xxxxxxxx>]

NMRbox (running ubuntu) has been able to upgrade nodes in the same series without long term issues.

Thereâs a transient outage when the master or our single access point is rebooted â e.g. condor_status doesnât work on a submit node, or shows empty. But in a few minutes it repopulates as everything gets synced up again.

(This is unofficial, and I have no idea whether it applies to servers in the Red Hat genus. ) 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Vechinski, Douglas <douglas.vechinski@xxxxxxxxxx>
Date: Thursday, May 7, 2026 at 11:05âAM
To: htcondor-users@xxxxxxxxxxx <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Procedure for upgrading between feature releases

*** Attention: This is an external email. ***

Use caution responding, opening attachments or clicking on links.

Report Suspicious

 

Iâm trying to find guidance on the process of upgrading a Condor pool. At the moment lets assume upgrading between feature releases of the same major version such as 25.x.y -> 25.x+a.y+b. The RPMSs are downloaded to a local repository and at some point every couple of months a general update process is applied to the machines for other packages as well (currently using RHEL 8 here). Letâs take 2 cases: A) the condor pool is idle, i.e. no jobs are actively running, B) the condor pool currently has jobs running.

 

Since things are upgraded via RPM packages I assume the executables simply get overwritten. Can condor_master be running on a machine and be upgraded or should it be stopped? Is there any particular order (machine)  that the Condor upgrades should occur? That is should the collector/negotiator be done first before any submit and/or execution machines or does it matter? Can an execute machine that is actively running jobs be updated live. If so, are there potential consequences? The jobs that we typically have running do not have the ability to be checkpointed.

This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.