Project

General

Profile

Bug #2249

frontend reconfig does not pick up Condor config changes

Added by Igor Sfiligoi over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
John Weigand
Category:
Frontend
Target version:
Start date:
12/01/2011
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

Hi all.

I just noticed that the
frontend.condor_config
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.

Igor

[1914] 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
[1914] frontend@glidein-frontend ~/frontstage/frontend_UCSD-o5_3a$ grep TRUSTED ~/glidecondor/etc/

/home/frontend/glidecondor/etc/condor_config.local:GSI_DAEMON_TRUSTED_CA_DIR=/etc/grid-security/certificates

History

#1 Updated by John Weigand over 8 years ago

Igor,

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.

Thanks
John Weigand

#2 Updated by Igor Sfiligoi over 8 years ago

  • Status changed from New to Closed

Works for me now, too!

Not sure what was the problem yesterday... I repeated exactly the same steps!
(maybe a dirty env)

Oh well... sorry for the false alarm.
Closing the ticket.

Igor

#3 Updated by Parag Mhashilkar over 8 years ago

  • Assignee set to John Weigand


Also available in: Atom PDF