9.2 Upgrading from the 7.6 series to the 7.8 series of Condor

While upgrading from the 7.6 series of Condor to the 7.8 series will bring many new features and improvements introduced in the 7.7 series of Condor, it will also introduce changes that administrators of sites running from an older Condor version should be aware of when planning an upgrade. Here is a list of items that administrators should be aware of.

• In the grid universe, the Amazon grid-type is gone and has been replaced with the EC2 grid-type. Also, support for grid-type gt4 (Web Services GRAM) has been removed.

• Default job submit options related to file transfers have changed. Across all platforms, defaults are now

    should_transfer_files = IF_NEEDED
    when_to_transfer_output = ON_EXIT
  

  See section 2.5.4 for details.

• On Linux and Mac OS, common utility code is now contained in a set of shared libraries. In the Linux native packages, most of these libraries are placed under /usr/lib[64]/condor and the RUNPATH attribute is set in the binaries to search there for them. In the tarball packages, these libraries are placed under lib and lib/condor, and the RUNPATH attribute is set in the binaries to search for them under the relative paths ../lib and ../lib/condor. This means that if you move or copy a Condor binary from a tarball package to a different location, you must do one of the following:
  • Move or copy the corresponding lib/ directory with it, or
  • Make a symlink in the new location pointing back to the original lib/ directory, or
  • Set environment variable LD_LIBRARY_PATH to point to the original lib/ and lib/condor/ directories
  One of the new shared libraries, libcondor_utils_7_8_0, has no .so versioning. Instead, the Condor version is included in the library name. This means that a Condor binary must always be matched with the libcondor_utils library from the same Condor release.

• The condor_hdfs service is no longer included within the Condor release. Instead, the Condor + HDFS integration previously bundled with version 7.6 is available in version 7.8 as a Contribution Module. Contribution Modules are optional packages that add functionality to Condor, but are provided and maintained outside of the core code base. See the Condor Wiki at https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=ContribModules.

• Previous to version 7.8, by default the condor_master would restart any individual daemon under its control if it notices that the file modification time of the binary for that daemon has changed. Now the condor_master will only monitor the file modification time of the condor_master binary itself. See section 3.10.1. Also, see MASTER_NEW_BINARY_RESTART on page .

• In DAGMan, if you have a PRE and a POST script on a node, the default now is that the POST script is run even if the PRE script failed. This change could impact unaware workflows such that POST scripts might erroneously report the node as succeeded. You can get the old behavior by setting DAGMAN_ALWAYS_RUN_POST to False. In addition, you can no longer directly submit a rescue DAG file with condor_submit_dag unless DAGMAN_WRITE_PARTIAL_RESCUE is set to False (not normally recommended). See section 2.10.

• The KILL expression cannot be used to grant more time to a job than offered by MachineMaxVacateTime . In Condor v7.8 and above, it is anticipated that most sites will simply use a default value of False for KILL and set MachineMaxVacateTime to control how long to wait. See page  for more information.