Submitter Ceiling (and Floor) using Python bindings (HTCondor 25.12.2)

[Bert DeKnuydt]

Dear Condorants,

I don't seem to manage to _get_ the submitter ceiling values in Python
from the htcondor.Negotiator().getPriorities() structure.

In old code, still with 'import htcondor' (not htcondor2), there was a
'Ceiling' field in what getPriorities returned; now it seems gone
(possibly since quite some time); the classadd of course still has
Ceiling (and Floor).

Did it move to some other place in the Python thing, or was it
(inadvertently?) dropped?

Cheers,

Bert.

[Todd L Miller]

> In old code, still with 'import htcondor' (not htcondor2), there was a
> 'Ceiling' field in what getPriorities returned; now it seems gone (possibly
> since quite some time); the classadd of course still has Ceiling (and Floor).

I'm confused. The return value of
htcondor.Negotiator.getPriorities() is a list of ClassAds, the same as
htcondor2.Negotiator.getPriorities(); which "the classad" are you talking
about?

> Did it move to some other place in the Python thing, or was it
> (inadvertently?) dropped?

If you ask condor_userprio (I don't know if you need to use -all
or not), what does it think the ceiling for the first (incomplete) entry
returned by htcondor2.Negotiator.getPriorities() is?*

-- Todd L Miller

*: It looks like, in an attempt to avoid having to update the bindings
every time we added or changed anything about user priorities, the
htcondor2 implementation introduced a bug where attributes missing
from the first ad** in the negotiator's reply aren't included in _any_
ad in the list.

**: For presumably good reasons that I'm not familiar with, the reply
from the negotiator to this query is not actually a list of ads, and
has to be translated by the client.