Bug 1101128 - Not customized agent configuration files should not be preserved after upgrade
Summary: Not customized agent configuration files should not be preserved after upgrade
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: JON3-45, PRODMGT-131, PRODMGT-417
TreeView+ depends on / blocked
 
Reported: 2014-05-26 08:32 UTC by Jan Bednarik
Modified: 2014-09-21 22:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-09 13:16:27 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.