frontend reconfig does not pick up Condor config changes
I just noticed that the
is not being recreated during reconfig (or even upgrade).
This is a problem if anything in the Condor configuration changes; there is currently no way to propagate it to the config used by the frontend.
 frontend@glidein-frontend ~/frontstage/frontend_UCSD-o5_3a$ grep TRUSTED
frontend.condor_config:GSI_DAEMON_TRUSTED_CA_DIR = /etc/osg/wn-client/globus/TRUSTED_CA
 frontend@glidein-frontend ~/frontstage/frontend_UCSD-o5_3a$ grep TRUSTED ~/glidecondor/etc/
#1 Updated by John Weigand about 8 years ago
Krista and I have tested this up and down and around.
It works fine!!
What we are seeing is that on a reconfig, if there is an
error, a message is displayed telling you the error (not
very obvious however) and then says the reconfig was OK.
Internally, due to the error, it does stop with the reconfig
and never updates the frontend.condor_config. So you then go
blissfully on your way.
Can you look closely at the reconfig doing?
And also verify that you have the CONDOR_CONFIG variable
set correctly to point to the CONDOR's condor config.