Bug 457265 - Rebase on Condor 7.0.4
Rebase on Condor 7.0.4
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
1.0
All Linux
high Severity urgent
: ---
: ---
Assigned To: grid-maint-list
Kim van der Riet
:
Depends On: 457141
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-30 12:04 EDT by Matthew Farrellee
Modified: 2008-08-11 13:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-11 13:55:20 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)

  None (edit)
Description Matthew Farrellee 2008-07-30 12:04:52 EDT
+++ This bug was initially created as a clone of Bug #457141 +++

http://www.cs.wisc.edu/condor/manual/v7.0/8_3Stable_Release.html

Version 7.0.4

Release Notes:

    * This release fixes a problem causing possible incorrect handling of wild
cards in authorization lists. Examples of the configuration variables that
specify authorization lists are

        ALLOW_WRITE
        DENY_WRITE
        HOSTALLOW_WRITE
        HOSTDENY_WRITE

      If a configuration variable uses the asterisk character (*) in
configuration variables that specify the authorization policy, it is advisable
to upgrade. This is especially true for the use of wild cards in any DENY list,
since this problem could result in access being allowed, when it should have
been denied. This issue affects all previous versions of Condor.

    * The default daemon-to-daemon security session duration has been changed
from 100 days to 1 day. This should reduce memory usage in the condor_ collector
in pools with short-lived condor_ startds (e.g. glidein pools or pools whose
machines are rebooted every night).

New Features:

    * Added functionality to periodically update timestamps on lock files. This
prevents administrative programs from deleting in-use lock files and causing
undefined behavior.

    * When the configuration variable SCHEDD_NAME ends in the @ symbol, Condor
will no longer append the fully qualified host name to the value. This makes it
possible to configure a high availability job queue that works with the remote
submission of jobs.

Configuration Variable Additions and Changes:

    * Added configuration variable: LOCK_FILE_UPDATE_INTERVAL. Please see page
[*] for a complete description.

    * Changed the default value of configuration variable
SEC_DEFAULT_SESSION_DURATION from 8640000 seconds (100 days) to 86400 seconds (1
day).

Bugs Fixed:

    * Fixed a bug in the condor_ c-gahp that caused it to fail repeatedly on
Windows, if more than two Condor-C jobs were submitted at the same time.

    * Fixed a problem that caused the condor_ collector's memory usage to
increase dramatically, if condor_ findhost was run repeatedly.

    * Fixed a bug where Windows jobs suspended by Condor would never be
continued, despite log files indicating successful continuation. This problem
has existed since the 6.9.2 release of Condor.

    * Fixed a problem that could cause condor_ dagman to core dump if straced,
especially if the dagman.out file is on a shared file system.

    * Fixed a problem introduced in 7.0.1 that could cause the condor_ schedd
daemon to crash when starting parallel or MPI universe jobs. In some cases, the
problem would result in the following log message:

      ERROR ``Assertion ERROR on (mrec->request_claim_sock == sock)'' \
        at line 1361 in file dedicated_scheduler.C

    * The condor_ procd daemon now periodically updates the timestamps on the
named pipe file system objects that it uses for communication. This prevents
these objects from being cleaned up by programs like tmpwatch, which would
result in Condor daemon exceptions.

    * Fixed a problem introduced in Condor 7.0.2 that would cause daemons to
fail on start up on Windows 2000.

    * Fixed a problem where standard universe jobs would fail to start when
using PrivSep, if the PROCD_ADDRESS configuration variable was not defined.

    * If the X509 proxy of a vanilla universe job has been refreshed, the
updated file will no longer be returned when the job completes.

    * If ClassAd attributes StreamOut or StreamErr are missing from the job
ClassAd of a grid universe job, the default value for these attributes is now False.

Known Bugs:

    * None.

Additions and Changes to the Manual:

    * None.


Version 7.0.3

Release Notes:

    * This is a bug fix release. A bug in Condor version 7.0.2 sometimes caused
the condor_ schedd to become unresponsive for 20 seconds when starting the
condor_ shadow to run a job. Therefore, anyone running 7.0.2 is strongly
encouraged to upgrade.

New Features:

    * None.

Configuration Variable Additions and Changes:

    * The configuration variable VALID_SPOOL_FILES now automatically includes
SCHEDD.lock, the lock file used for high availability condor_ schedd fail over.
Other high availability lock files are not currently included.

Bugs Fixed:

    * Fixed a problem sometimes causing minutes or more of lag between the time
of job suspension or unsuspension and the corresponding entries in the job user log.

    * Fixed a problem in condor_ q -better-analyze handling requirements
expressions containing the expression =!= UNDEFINED.

    * Configuration variable GRIDMANAGER_GAHP_CALL_TIMEOUT is now recognized for
nordugrid grid universe jobs.

    * Fixed a bug that could cause the condor_ schedd daemon to abort and
restart some time after a graceful restart, when jobs to which the condor_
schedd daemon reconnected were preempted.

    * Fixed a bug causing failure to reconnect to jobs which use
$$([expression]) in their ClassAds. The jobs would go on hold with the hold
reason: "Cannot expand $$([expression])."

    * Fixed a bug in Condor version 7.0.2 that sometimes caused the condor_
schedd daemon to become unresponsive for 20 seconds when starting the condor_
shadow daemon to run a job.

Known Bugs:

    * None.

Additions and Changes to the Manual:

    * See section 4.4.1 for documentation on finding the port number the condor_
schedd daemon is listening on for use with the web service API.
Comment 3 errata-xmlrpc 2008-08-11 13:55:20 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 the 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-2008-0816.html

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