[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Failed to apply a required job transform

The bug fix here https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=6719
Doesn't actually fix the failure of the submit transform. 
That is apparently a different bug which I'll be looking into shortly.

I should point out that the use of multiple queue statements in a submit file isn't necessary
and is a fairly old form that we would really like to get rid of.   The complex queue statements
that we added several years ago is a better way to do things.

This submit file works just fine and doesn't produce multiple clusters

   Transfer_Executable = false
   queue executable from (

This submit file doesn't have trouble with transforms.  I just checked in our production pool


-----Original Message-----
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Todd Tannenbaum
Sent: Wednesday, June 19, 2019 3:44 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>; Alessandro Italiano <alessandro.italiano@xxxxxxxxxx>
Subject: Re: [HTCondor-users] Failed to apply a required job transform

On 6/19/2019 5:10 AM, Alessandro Italiano wrote:
> Hi,
> we have deployed in production job transform in order to define in a 
> administrative manner the accounting group.
> Since that we have introduced this feature, some users are reporting the 
> following error:
> [italiano@tmp htcondor]$ condor_submit submit.try
> Submitting job(s)...
> ERROR: Failed to commit job submission into the queue.
> ERROR: Failed to apply a required job transform.
> In particular the error is raised every time the submit file contains 
> multiple queue command whit different executable command.
> for instance
> universe=vanilla
> Transfer_Executable = false
> executable=/bin/env
> queue
> executable=/bin/id
> queue

Indeed, this sounds like a bug that was patched in HTCondor v8.9.1+

The patch will also appear in the v8.8 series starting with v8.8.4 
scheduled to be released to the web next week.

The ticket with details regarding this bug is here:

Having said this, I think another bug is in the documentation -- I don't 
think it should have ever been documented that changing the executable 
within a single submit file oddly results in a new job cluster.  In 
fact, I don't think changing the executable within a single submission 
should be allowed.  If possible, please try to avoid changing the 
executable within one submit file (job cluster).  While it works today, 
I definitely can imagine a tomorrow where this will cease working.

Hope the above helps

HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: