Bug 1101128

Summary:	Not customized agent configuration files should not be preserved after upgrade
Product:	[Other] RHQ Project	Reporter:	Jan Bednarik <jbednari>
Component:	Agent	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	hrupp, mkoci
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-09 13:16:27 UTC	Type:	Bug
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:	823965

Description Jan Bednarik 2014-05-26 08:32:50 UTC

Description of problem:
When upgrading RHQ server from version 4.9 to 4.11, the agent's configuration files 'agent-configuration.xml' and 'log4j.xml' get preserved even if they were not changed by user.

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

How reproducible:
always

Steps to Reproduce:
1. Install RHQ server 4.9
2. Upgrade to RHQ server 4.11
3. Check that there are two new files 'agent-configuration.xml.new' and 'log4j.xml.new' present in the directory ~/rhq-agent/conf.

Actual results:
Files 'agent-configuration.xml.new' and 'log4j.xml.new' representing new agent's configuration are present along the old untouched configuration files 'agent-configuration.xml' and 'log4j.xml'.

Expected results:
Only two files named as 'agent-configuration.xml' and 'log4j.xml' representing new agent's configuration are present and the old configuration files are not preserved.

Additional info:

Comment 1 Jan Bednarik 2014-09-09 13:16:27 UTC

Moving to CLOSED.

According to newly set criteria for the behaviour of this feature (see BZ 823965 - comments 22 and 23) this is not a bug anymore.