[HTCondor-users] IS_OWNER not stopping jobs from running

[Andrew Pickford <andrewp@xxxxxxxxx>]

Hi All,

I've run into a potential issue with the IS_OWNER setting. I'm setting 
IS_OWNER to true on an execute node in my test cluster but the node is 
still starting jobs. The condor cluster is running condor v24.3.0 and on 
the node START = true and IS_OWNER = true are explicitly set in the 
config. I then see with condor_status (output trimmed to the node in 
question):

[andrewp@vaars-15 test]$ condor_status
Name            OpSys   Arch ÂState  ÂActivity LoadAv 
Mem  ÂActvtyTime
slot1@xxxxxxxxxxxxxxxxxxxxx LINUX   X86_64 Owner  ÂIdle 0.000 
185069Â 0+00:06:31

so the owner state is set correctly, but then after submitting a job:

[andrewp@vaars-15 test]$ condor_status
Name             OpSys   Arch ÂState  ÂActivity 
LoadAv Mem  ÂActvtyTime

slot1@xxxxxxxxxxxxxxxxxxxxx ÂLINUX   X86_64 Owner  ÂIdle  0.000 
183021Â 0+00:07:23
slot1_1@xxxxxxxxxxxxxxxxxxxxx LINUX   X86_64 Claimed ÂBusy  0.000 
Â2048Â 0+00:00:00

According to the documentation page for the Configuration for Execution 
Points, setting IS_OWNER to true should stop an execute node from 
accepting jobs. I'm not sure if I'm misreading the documentation here, 
or I've found a bug or maybe the partitionable slots that are configured 
for the execute node are not picking up the owner state correctly? Or 
something else. My first question is am I correct about IS_OWNER, should 
that stop jobs from starting?


Thanks,

Andrew