Uploaded image for project: 'SPI'
  1. SPI
  2. SPI-1986

Condor Configuration provided in nightlies does break other condor systems

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Low
    • Resolution: Fixed
    • LCG Views
    • None
    • ANY

    Description

      Hi,

      I currently have a problem when using nightly builds from cvmfs like

      source /cvmfs/sft-nightlies.cern.ch/lcg/views/dev3/latest/x86_64-centos7-gcc9-opt/setup.sh
      

       

      After setting this env, the condor system at our local institute cannot be used anymore, because within the nightly, several condor parameters are set like

       

       

      echo $CONDOR_CONFIG
      /eos/project/l/lxbatch/public/config-condor-swan/condor_config
      

       

      which is not compatible with other systems:

       

       

      condor_q
      File specified in CONDOR_CONFIG environment variable:
      "/eos/project/l/lxbatch/public/config-condor-swan/condor_config" does not exist.
      

       

      even after unsetting the $CONDOR_CONFIG variable, some additional config parameters seem to be set, preventing me from using our local condor batch system.

       

       

      condor_q
      Error: use security:recommended_v9_0: does not recognise recommended_v9_0
      Config source Error "/etc/condor/config.d/00-htcondor-9.0.config", Line 26: at use security:recommended_v9_0:recommended_v9_0
      Configuration Error Line 26 while reading config source /etc/condor/config.d/00-htcondor-9.0.config
      

       

      My guess is, this is due to the addition of condor to the nightly builds as requested here:

      https://sft.its.cern.ch/jira/browse/SPI-1915

      Attachments

        Activity

          People

            sailer Andre Sailer
            sbrommer Sebastian Brommer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: