Bug 610189

Summary:	Upgrading condor for use with Remote Configuration
Product:	Red Hat Enterprise MRG	Reporter:	Robert Rati <rrati>
Component:	Release_Notes	Assignee:	Lana Brindley <lbrindle>
Status:	CLOSED WONTFIX	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	low
Version:	Development	CC:	mhideo
Target Milestone:	1.3	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	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).	Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-22 00:15:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	548214

Description Robert Rati 2010-07-01 17:46:20 UTC

Description of problem:
If the Remote Configuration feature is to be used on a machine that either A) condor is being upgraded where custom configuration has been applied in /var/lib/condor/condor_config.local or B) has the Remote Configuration feature installed then special care must be taken to ensure proper functioning of the Remote Configuration feature.

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).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Lana Brindley 2010-09-17 00:40:34 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
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).

Comment 2 Robert Rati 2010-09-21 20:08:36 UTC

This release note is no longer needed.  The condor_config.local file is not used anymore, and the upgrade case is covered by 628052.