Bug 1093781 - Update RPM to maintain existing agent-configuration.xml and log4j.xml files after agent update/upgrade
Summary: Update RPM to maintain existing agent-configuration.xml and log4j.xml files a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.1.0,JON 3.1.1,JON 3.1.2
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ER01
: JON 3.3.0
Assignee: Stefan Negrea
QA Contact: Armine Hovsepyan
URL:
Whiteboard:
Depends On:
Blocks: JON3-45, PRODMGT-131, PRODMGT-417
TreeView+ depends on / blocked
 
Reported: 2014-05-02 15:56 UTC by Stefan Negrea
Modified: 2019-08-15 03:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: JON3-45, PRODMGT-131, PRODMGT-417
Environment:
Last Closed: 2014-12-11 14:02:45 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JON3-45 0 Major Verified agent-configuration.xml and log4j.xml files preservation during agent upgrade/update [PRODMGT-417] 2017-03-31 11:46:18 UTC
Red Hat Issue Tracker PRODMGT-131 0 Major Closed Maintain existing agent-configuration.xml and log4j.xml files after agent update/upgrade 2017-03-31 11:46:18 UTC
Red Hat Issue Tracker PRODMGT-417 0 Major Closed agent-configuration.xml and log4j.xml files preservation during agent upgrade/update 2017-03-31 11:46:18 UTC
Red Hat Knowledge Base (Solution) 550713 0 None None None Never

Comment 3 Simeon Pinder 2014-07-31 15:51:59 UTC 
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
Comment 5 Jan Bednarik 2014-08-21 14:34:45 UTC 
Moving to VERIFIED

Tested on jboss-on-agent-3.3-3.3.0.ER01-2.el6_5.noarch.rpm package.
Comment 6 JBoss JIRA Server 2014-08-21 15:27:46 UTC 
mfoley user <mfoley> updated the status of jira JON3-45 to Reopened
Comment 7 JBoss JIRA Server 2014-09-09 13:27:12 UTC 
mfoley user <mfoley> updated the status of jira JON3-45 to Resolved
Note You need to log in before you can comment on or make changes to this bug.