Re: [HTCondor-users] Missing x509* attributes in routed jobs

[Stefano Dal Pra <stefano.dalpra@xxxxxxxxxxxx>]

Il 20/03/23 19:46, John M Knoeller via HTCondor-users ha scritto:

> Jaime and I looked at the code and we don't see any way that these attributes can be cleared once set unless you are running a version of HTCondor from about 10 years ago.  
>
> Are you sure that the routed job ever had the X509UserProxyVOName attribute?
>     
    
X509UserProxyVOName is undefined on jobs whose jobstatus moved 2 --> 5:
    [root@ce04-htc
        ~]# condor_q -cons 'acctgroup == "belle" &&
        x509UserProxyVOName =?= undefined' -lim 1 -af:j lastjobstatus
        jobstatus routedfromjobid
      
      9335490.0 2 5 4833703.48
      
      
      The corresponding CE job has x509* attributes:
      [root@ce04-htc ~]# condor_ce_q 4833703.48 -l | egrep '^x509'
      
      x509userproxy =
        "tmp6lK7rx"
      
      x509UserProxyEmail =
        "****@***.kek.jp"
      
      x509UserProxyExpiration
        = 1665422180
      
      x509UserProxyFirstFQAN
        = "/belle/Role=production/Capability=NULL"
      
      x509UserProxyFQAN =
        "/C=JP/O=KEK/OU=CRC/CN=Robot: BelleDIRAC Pilot -
******,/belle/Role=production/Capability=NULL,/belle/Role=NULL/Capability=N
      ULL"
      
      x509userproxysubject
        = "/C=JP/O=KEK/OU=CRC/CN=Robot: BelleDIRAC Pilot - *******"
      
      x509UserProxyVOName
        = "belle"
      
    #There are no
        running jobs without x509UserProxyVOName:
            
          [root@ce04-htc ~]# condor_q -cons 'acctgroup ==
        "belle" && jobstatus == 2 && x509UserProxyVOName
        =?= undefined' -lim 1 -af:j lastjobstatus jobstatu
      s routedfromjobid
      
    Stefano
    
    
> -tj
>
> -----Original Message-----
> From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Stefano Dal Pra
> Sent: Thursday, March 16, 2023 11:52 AM
> To: htcondor-users@xxxxxxxxxxx
> Subject: [HTCondor-users] Missing x509* attributes in routed jobs
>
> Hello,
> condor-9.0.17-1.el7, htcondor-ce-5.1.6-1.el7 here.
>
> I have job history files (routed jobs) without x509* attributes.
> I looked into that a bit more and it looks like x509* are lost when 
> jobstatus moves 2 --> 5.
>
> Example:
> [root@ce04-htc ~]# condor_q -cons 'acctgroup == "belle"' -af jobstatus 
> x509userproxyvoname | sort | uniq -c
>  ÂÂÂÂ 46 2 belle
>  ÂÂÂ 322 5 undefined
>
> [root@ce04-htc ~]# condor_history -cons 'acctgroup == "belle"' -af 
> lastjobstatus jobstatus x509userproxyvoname | sort | uniq -c
>  ÂÂÂ 197 2 4 belle
>  ÂÂ 2256 5 3 undefined
>
> [root@ce03-htc ~]# condor_q -cons 'x509UserProxyVOName =?= undefined' 
> -af acctgroup jobstatus | sort -u
> atlas 1
> belle 3
> belle 5
>
> [root@ce03-htc ~]# condor_ce_q -cons 'regexp("belle",owner)' -af 
> x509UserProxyVOName | sort -u
> belle
>
> The jobs in the condor queue have the x509UserProxyVOName attribute when 
> routed by the condor-ce,
> but this seems to disappear when the job moves from jobstatus 2 to 5.
>
> This is happening with belle only right now, but i have seen that 
> happening with other VOs too, all of them using Dirac.
>
> Any clue on why this could be happening?
>
> Thanks
> Stefano
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/
>