Yes. Late materialization is very incomplete and only works for the simplest jobs. It does not work with x509 proxies at this time.
This is one of the reasons that it is not yet documentedâ.
The only place I can find the mistyped knob name that you mention in the HTCondor git repo (which includes the docs) is in a comment
on one of our unit tests.
The correct knob name is indeed SCHEDD_ALLOW_LATE_MATERIALIZE, and it defaults to true
in the 8.8 and 8.9 releases.
This knob will be removed entirely once late materialization work is complete.
For now, the only reason to set the knob is to disable it..
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Kenyi Paolo HurtadoAnampa
Sent: Friday, March 1, 2019 2:50 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] v8.8/9 Late materialization documentation typo (and bug/error)?
Just to update on the late materialization + x509 user proxies.
If I change the owner of my proxy file to "condor" (rather than my own username), then the proxy can be read.
This only happens if I try to use late materialization, so it seems like a bug.
If so, how do I report the issue by the way (or is this mail-list the right way for reporting issues)?.
Thanks in advance for the support!
On Fri, Mar 1, 2019 at 3:32 PM Kenyi Paolo HurtadoAnampa <khurtado@xxxxxx> wrote:
I'm reading the documentation on late materialization available for HTCondor 8.7.4+ and noticed it says the schedd needs the following:
SCHEDD_ALLOW_LATE_MATERIALIZATION = true
However, the real knob seems to be (at least from my tests):
SCHEDD_ALLOW_LATE_MATERIALIZE = true
Also, when I try to submit jobs that require a grid proxy to be forwarded using this feature (using "max_materialize = 4" in my submit file), I get an "unable to read proxy file" error that doesn't happen when "SCHEDD_ALLOW_LATE_MATERIALIZE
= false". The error is the following:
TriggerEventTypeNumber = 35
037 (1532.-01.000) 03/01 21:22:04 Job Materialization Paused
failed to create ClassAd for Job 1532.0 : Submit:-1:unable to read proxy file
028 (1532.-01.000) 03/01 21:22:04 Job ad information event triggered.
JOB_Site = "$$(GLIDEIN_Site:Unknown)"
JOB_GLIDEIN_Name = "$$(GLIDEIN_Name:Unknown)"
Reason = "failed to create ClassAd for Job 1532.0 : Submit:-1:unable to read proxy file
My proxy has the typical patter /tmp/x509up_$(id -u $USER) and has the right ownership/permissions.
If I comment the x509proxy line in my submit file, then I see 4 jobs materialized! But of course, those will stay Idle forever because of the missing proxy.