CAUSE: If the Remote Configuration feature is to be used on a machine that has had a custom configuration applied in /var/lib/condor/condor_config.local or has had the Remote Configuration feature installed previously.
CONSEQUENCE: The Remote Configuration feature might not function correctly after upgrading.
FIX: Workaround: If a previous version of remote configuration has been installed, the condor_config.local file will need to be replaced with the version in the new
condor RPM. Upon upgrading condor, this file should be created as condor_config.local.rpmnew and contain the LOCAL_CONFIG_DIR parameter.
If condor_config.local has been modified outside of the remote configuration feature, then upon upgrading condor the packaged version of condor_config.local should be created as condor_config.local.rpmnew. The differences between the
two files should be merged, and the resulting condor_config.local should contain the LOCAL_CONFIG_DIR parameter defined in the condor_config.local.rpmnew file.
After the changes to condor_config.local have been addressed, configuration of the Remote Configuration feature may continue as normal (ie setting QMF_BROKER_HOST).