Re: [HTCondor-users] Credd discovery in 24.0

[Antonio Delgado Peris <Antonio.Delgado.Peris@xxxxxxx>]

Hi Todd.

Thanks a lot.

Antonio

> -----Original Message-----
> From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of
> Todd L Miller via HTCondor-users
> Sent: Monday, 16 December 2024 20:17
> To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
> Cc: Todd Lancaster Miller <tlmiller@xxxxxxxxxxx>
> Subject: Re: [HTCondor-users] Credd discovery in 24.0
> 
> > Clients running v23.10 or v24.0 do work properly, so if this just to
> > be expected we will need to assume that we need to update clients
> > before CMs.
> 
> [...]
> 
> > Notice that in the latter case, the 'sock=schedd_2717527_10f7' bit
> > seems wrong (should be 'sock=credd_...'), and this leads to:
> 
>  	This is a bug (HTCONDOR-2497) which we fixed in the 23.x series but
> neglected to fix for forwards-compability.  It'll be fixed in the next 23.0.x release.
> 
> > I have also noticed that if a query a CM using condor_status, v23.0
> > CMs will provide the credd classad when asked with either '-subsystem credd'
> > or '-subsystem CredD', but v24.0 CMs will only provide the classad if
> > '-subsystem CredD' is used. This happens with either 23.0 or 24.0
> > clients. This may be related to the described issue or not.
> 
>  	This appears to be an unrelated bug, which we've identified and intend
> to fix.
> 
> -- ToddM
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> 
> The archives can be found at: https://www-auth.cs.wisc.edu/lists/htcondor-
> users/