Re: [HTCondor-users] Condor_config_val stopped working after updating to 8.4.7

[John M Knoeller <johnkn@xxxxxxxxxxx>]

What does

 

    condor_config_val  -verbose âname <node-name> -startd âdump _CONFIG   SETTABLE_

 

return for that node?

 

From looking at the log snipped, it appears that you are being authorized as ALLOW and not ADMINISTRATOR,

So the content of SETTABLE_ATTRS_ADMINISTRATOR isnât relevant. It would need to just be SETTABLE_ATTRS.

 

I donât know a lot about how the security code to know what would have changed between 7.4.4 and 8.4

From my reading of the code this config should never have worked.

 

-tj

 

 

From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of mohammad kashif
Sent: Tuesday, August 9, 2016 5:56 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Condor_config_val stopped working after updating to 8.4.7

 

Hi

I use condor_config_val to manage compute nodes remotely. I upgraded some of compute nodes to 8.4.7 and 8.4.8 and condor_config_val -set stopped working
 

condor_config_val -name <node-name> -startd -set "StartJobs = True"  Attempt to set configuration "StartJobs = True" on startd slot1@<node_name> A.B.C.D:62166?addrs=A.B.C.D-62166> failed.

I have following config settings which is working for 8.4.4

ENABLE_RUNTIME_CONFIG = TRUE

STARTD.SETTABLE_ATTRS_ADMINISTRATOR = StartJobs

ENABLE_PERSISTENT_CONFIG = TRUE

PERSISTENT_CONFIG_DIR = /etc/condor/persistent

Has any one else seen this issue?

Thanks

Kashif