Re: [Condor-users] EVENT_LOG_JOB_AD_INFORMATION_ATTRS not being honored

[Dan Bradley <dan@xxxxxxxxxxxx>]

Hi Derek,

> I have EVENT_LOG_JOB_AD_INFORMATION_ATTRS set to include an attributed defined in the condor_config.local: 
> JOBGLIDEIN_Site='$$([IfThenElse(IsUndefined(TARGET.GLIDEIN_Site), "Local Job", TARGET.GLIDEIN_Site)])'
>   

Do you really have single quotes around the value of JOBGLIDEIN_Site?  I 
would have expected double quotes.

> I then have it added to the submit:
> SUBMIT_EXPRS = $(SUBMIT_EXPRS) PeriodicHold JOBGLIDEIN_Site
>
> Finally, I have it added to the event log:
> EVENT_LOG_JOB_AD_INFORMATION_ATTRS=Owner,CurrentHosts,x509userproxysubject,AccountingGroup,GlobalJobId,QDate,JobStartDate,JobCurrentStartDate,JobFinishedHookDone,MATCH_EXP_JOBGLIDEIN_Site,RemoteHost
>
> For 1 user on the system, this all just works, and the MATCH_EXP_JOBGLIDEIN_Site is added to the event log.  For another user, it doesn't include the MATCH_EXP_JOBGLIDEIN_Site, but it includes all other attributes.
>
> The one user that it doesn't work for using DAGMAN.  He has no eventlog variables defined in the condor submit file.  condor_config_val -dump reports the eventlog lines above are set correctly, and that condor is reading from the correct config values.
>   

Is it the scheduler universe DAGMan job itself that lacks 
MATCH_EXP_JOBGLIDEIN_Site, or is it a job submitted by DAGMan that lacks it?

I wouldn't expect any scheduler universe job to have 
MATCH_EXP_JOBGLIDEIN_Site, because no matchmaking takes place for such 
jobs.  On the other hand, I would expect it to be there for vanilla 
universe jobs submitted by the DAGMan.

Also, if you look at the job with condor_history -long, do you see that 
it is missing both JOBGLIDEIN_Site and MATCH_EXP_JOBGLIDEIN_Site?  Or is 
it only missing the latter?

--Dan